# CVE-2026-72825: Grav API Plugin before 1.0.13 API-key scope cap bypass via ReportsController

> Least-privilege API keys can bypass scope restrictions to modify Twig sandbox allowlists, enabling Server-Side Template Injection and remote code execution.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:L/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:** 29 Oct 2026
- **Also known as:** GHSA-rv98-5gw8-6hf9

## What is CVE-2026-72825?

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

### Official description

The getgrav/grav-plugin-api plugin before 1.0.13 contains an API-key scope cap bypass in the POST /reports/twig-content/allowlist endpoint (ReportsController). The endpoint enforces requirePermission('api.config.write') followed by a bare isSuperAdmin() check instead of requireSuper(). Because isSuperAdmin() reads access.api.super directly and never consults api_key_scopes, a least-privilege API key scoped to api.config.write minted on a super account passes the gate, allowing an attacker to append attacker-chosen tokens to the security.twig_sandbox allowlist (persisted to user/config/security.yaml). Widening the allowlist turns any subsequent Twig-in-content render into an SSTI/RCE sink.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-72825 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72825 is a high-severity missing authorization vulnerability in getgrav grav-plugin-api, 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-72825 exists.

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

## Sources

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

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