# CVE-2026-62233: grav-plugin-api < 1.0.6 Privilege Escalation via createApiKey

> Non-super-admin users can escalate to super-admin by minting API keys or disabling 2FA due to missing authorization checks in the Grav API plugin.

- **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:** 17 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-qrm9-ppgh-qwm9

## What is CVE-2026-62233?

CVE-2026-62233 is a high-severity vulnerability in getgrav grav, published on 17 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

grav-plugin-api before 1.0.6 fails to validate super-admin status in createApiKey, generate2fa, and disable2fa endpoints, allowing non-super api.users.write managers to escalate to super-admin. Attackers can mint API keys bound to super-admin accounts or strip 2FA from super-admin users to achieve full instance takeover.

Weakness: CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-62233 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-62233 is a high-severity vulnerability in getgrav grav, published on 17 Jul 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-62233 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-62233/ (Markdown: https://insights.sbomify.com/CVE-2026-62233/index.md)
```

## Sources

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

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