# CVE-2026-72824: Grav before 1.0.13 API Key Scope Bypass via PagesController

> Least-privilege API keys can bypass scope restrictions to enable Twig processing, leading to server-side template injection and remote code execution.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/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:** 14 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-qpvv-mv8x-vg3c

## What is CVE-2026-72824?

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

### Official description

The Grav API plugin (getgrav/grav-plugin-api) before 1.0.13 contains an API key scope-cap bypass in PagesController::guardTwigContent(). The Twig-toggle check uses a bare isSuperAdmin() gate that does not consult api_key_scopes, so a least-privilege API key scoped only to api.pages.write and minted on a super account can enable process.twig on a page save even though admin.pages_twig is intentionally outside the api.pages scope. When security.twig_content.process_enabled=true and editor_enabled=false, this allows Twig-in-content to execute server-side, resulting in server-side template injection (SSTI) and remote code execution.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-72824 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72824 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72824 is a high-severity missing authorization vulnerability in getgrav grav, published on 14 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72824 exists.

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-72824/ (Markdown: https://insights.sbomify.com/CVE-2026-72824/index.md)
```

## Sources

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

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