# CVE-2026-72830: Grav API Plugin before 1.0.13 RCE via ConfigController scope bypass

> Attackers with scoped API keys can bypass permission checks to inject commands into the scheduler, achieving 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-q6cm-x4f7-73r6

## What is CVE-2026-72830?

CVE-2026-72830 is a high-severity 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

Grav API plugin versions before 1.0.13 fail to enforce API key scope caps in ConfigController super-scope gates, allowing scoped keys to write scheduler configuration. The scope cap is applied only inside requirePermission(), while the scheduler and backups gates use a bare isSuperAdmin() check that never consults api_key_scopes. An attacker holding an API key scoped to api.config.write that was minted on a super account can therefore inject arbitrary commands into scheduler.custom_jobs, which Job::run() passes to a Symfony Process, achieving operating system command execution as the web server user.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-72830 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72830 is a high-severity 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-72830 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-72830/ (Markdown: https://insights.sbomify.com/CVE-2026-72830/index.md)
```

## Sources

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

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