Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-114659 Overview
CVE-2026-114659 is an authorization bypass vulnerability in the Grav Flex Objects plugin, affecting versions 1.4.0 through 1.4.16. The flaw resides in the generic /api/v1/flex-objects/pages API routes, which only validate directory-level admin.pages permissions. These routes fail to enforce the Pages API's api.pages.read and api.pages.write permissions or page-level permission rules. Authenticated non-super users holding api.access combined with admin.pages or admin.configuration.pages permissions can read page source and frontmatter, modify content, or delete pages they are otherwise denied. The weakness is classified under [CWE-424: Improper Protection of Alternate Path].
Critical Impact
Authenticated low-privilege users can bypass page-level access controls to read, modify, or delete restricted content via the Flex Objects API.
Affected Products
- Grav CMS Flex Objects plugin version 1.4.0
- Grav CMS Flex Objects plugin versions up to and including 1.4.16
- Grav CMS installations exposing the Admin API with multi-user role separation
Discovery Timeline
- 2026-10-22 - CVE CVE-2026-114659 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-114659
Vulnerability Analysis
Grav is a flat-file content management system (CMS), and the Flex Objects plugin provides generic REST endpoints for managing structured content including pages. The plugin exposes /api/v1/flex-objects/pages as an alternate route for page operations, parallel to the dedicated Pages API. The generic route evaluates only directory-level admin permissions and skips the finer-grained authorization checks the Pages API enforces. As a result, access decisions made on individual pages or through the api.pages.read and api.pages.write scopes do not apply when requests arrive via the Flex Objects path.
Root Cause
The root cause is a missing authorization check on an alternate code path, aligned with [CWE-424]. The Flex Objects route handler trusts the broad admin.pages or admin.configuration.pages permission as sufficient. It never calls the Pages API permission layer, nor does it iterate page-level permission rules declared in page frontmatter or site configuration. Authorization logic is therefore duplicated inconsistently between two parallel API surfaces.
Attack Vector
Exploitation requires an authenticated account with api.access and either admin.pages or admin.configuration.pages granted. The attacker issues HTTP requests to /api/v1/flex-objects/pages endpoints to read restricted page source and frontmatter, perform PATCH or PUT modifications, or send DELETE requests against pages their role-based access control should deny. No user interaction and no additional privileges beyond standard editor-tier roles are required. The vulnerability manifests entirely at the API layer. Refer to the GitHub Security Advisory GHSA-2pvc-r9gj-mcpf and the VulnCheck Advisory on Grav Flex Objects for the full technical write-up.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-114659
Indicators of Compromise
- HTTP requests from non-super user sessions to /api/v1/flex-objects/pages endpoints targeting pages outside the user's assigned scope.
- Unexpected PATCH, PUT, or DELETE operations against page objects in Grav admin audit logs attributed to editor-tier accounts.
- Modified or missing page files on disk whose last-editor metadata does not match the account that normally maintains them.
Detection Strategies
- Enable verbose logging on the Grav admin plugin and alert on any /api/v1/flex-objects/pages traffic originating from accounts without super role.
- Correlate Flex Objects API calls with the authenticated user's declared page-level permissions to flag mismatches.
- Review web server access logs for high-volume enumeration of flex-object page identifiers by a single session.
Monitoring Recommendations
- Baseline normal API usage per role and alert on deviations in request method distribution.
- Monitor file-system changes under the user/pages/ directory and reconcile against expected editorial workflows.
- Track authentication events for accounts holding api.access combined with admin.pages or admin.configuration.pages permissions.
How to Mitigate CVE-2026-114659
Immediate Actions Required
- Upgrade the Grav Flex Objects plugin to version 1.4.17 or later on all Grav installations.
- Audit all user accounts and remove api.access, admin.pages, and admin.configuration.pages permissions from roles that do not require full page management.
- Review recent page modifications, deletions, and content changes to identify unauthorized actions performed prior to patching.
Patch Information
The maintainers addressed the issue in Flex Objects plugin version 1.4.17 by enforcing api.pages.read and api.pages.write permissions on the generic Flex Objects page routes and applying page-level permission rules. Apply the update through the Grav Package Manager (bin/gpm update flex-objects) or by replacing the plugin directory with the fixed release. Validation details are documented in the GitHub Security Advisory GHSA-2pvc-r9gj-mcpf.
Workarounds
- Restrict network access to the Grav /api/v1/flex-objects/ path to trusted administrators via reverse-proxy ACLs until the patch is applied.
- Temporarily revoke api.access from non-super users to prevent any Flex Objects API invocation.
- Disable the Flex Objects plugin on sites where the Pages API is not actively required.
# Configuration example: upgrade Flex Objects via Grav Package Manager
bin/gpm update flex-objects
bin/gpm version flex-objects # confirm >= 1.4.17
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

