# CVE-2026-114659: Grav Flex Objects 1.4.0 before 1.4.17 Authorization Bypass via Pages API Routes


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-7hqv-ch9q-jw4v

## What is CVE-2026-114659?

CVE-2026-114659 is a high-severity vulnerability in getgrav grav-plugin-flex-objects, published on 22 Oct 2026. 

### Official description

Grav Flex Objects plugin 1.4.0 before 1.4.17 contains an authorization bypass because its generic /api/v1/flex-objects/pages API routes check only directory-level admin.pages permissions, without enforcing the Pages API's api.pages.read/write permissions or page-level permissions rules. Authenticated non-super users with api.access and admin.pages or admin.configuration.pages permissions can read page source and frontmatter, modify content, or delete pages they are denied.

Weakness: CWE-424 (Improper Protection of Alternate Path)

## Which versions are affected by CVE-2026-114659?


## How do I fix CVE-2026-114659?

No fix has been published for CVE-2026-114659 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-114659 being exploited?

There is no known exploitation of CVE-2026-114659 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114659 and fix it if it is affected.

What it is: CVE-2026-114659 is a high-severity vulnerability in getgrav grav-plugin-flex-objects, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114659 in the wild and no public exploit code.

Affected product: getgrav grav-plugin-flex-objects. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-114659/ (Markdown: https://insights.sbomify.com/CVE-2026-114659/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-114659
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-114659
- OSV: https://osv.dev/vulnerability/CVE-2026-114659

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-114659/
Summaries are generated and may contain mistakes; the official description above is the record.