# CVE-2026-56707: Grav Flex Objects 1.4.0 through 1.4.7 Authorization Bypass via Shortcode

> Attackers with page-edit access can bypass authorization checks to expose sensitive user account information via a shortcode.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-f549-r4pw-jw3m, GHSA-x929-528m-vx2m

## What is CVE-2026-56707?

CVE-2026-56707 is a high-severity missing authorization vulnerability in getgrav grav, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Grav Flex Objects plugin versions 1.4.0 through 1.4.7 contain an authorization bypass vulnerability in the flex-objects shortcode that allows users with page-edit access to render any registered Flex collection without permission checks. Attackers can place the shortcode in published pages to expose sensitive directory contents including user account information, bypassing the authorize ACL enforced in the admin panel.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-56707 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56707 is a high-severity missing authorization vulnerability in getgrav grav, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-56707 in the wild and no public exploit code.

Affected product: getgrav grav. 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-56707/ (Markdown: https://insights.sbomify.com/CVE-2026-56707/index.md)
```

## Sources

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

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