The CVE identifies a privilege escalation in Grav's API plugin where four endpoints use isSuperAdmin() to bypass permission scoping entirely — read-only API keys can perform write actions if the underlying account has super-admin privileges. The 8.8 CVSS is accurate, but the real exposure isn't the four controllers; it's the parallel authorization architecture that allowed this pattern to exist at all. These endpoints were almost certainly gated only by isSuperAdmin() when the plugin was admin-only, and requirePermission() was bolted on later for API key scoping. The early-return pattern isn't negligence — it's a legacy migration artifact common to systems that add capability-based authorization after identity-based gates are already entrenched. The 1.0.13 patch adds requirePermission() calls to the four known endpoints, which closes the immediate bypass but leaves the broader architectural problem untouched: isSuperAdmin() still executes as a parallel gate elsewhere in the plugin, and the underlying authorization paradigm collision — identity checks versus capability assertions — remains unresolved. More critically, the EPSS of 0.00261 measures external exploitation, not credential-valid exploitation. A read-only key minted against a super-admin account before patching is still a valid credential that can now be tested against the same system it was issued for. Organizations should treat every pre-1.0.13 scoped key on super-admin accounts as compromised infrastructure and rotate them. The plugin's authorization layer needs a structural fix — isSuperAdmin() should either enforce scope checks or be deprecated with architectural signals preventing future use, not patched case-by-case.
CVE-2026-72833
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Grav API plugin (getgrav/grav-plugin-api) versions >= 1.0.6 and <= 1.0.11 contain a privilege escalation vulnerability. A scoped API key minted on a super-admin account bypasses its declared scope cap on four isSuperAdmin()-gated write endpoints (in GroupsController, AccountsConfigController, PreferencesController, and DashboardWidgetController). These endpoints authorize via a super-admin early-return that never invokes requirePermission()—the sole enforcement point of the scope cap—so a 'read-only'-scoped key (e.g. api.pages.read) can perform super-only write operations, including rewriting group ACL maps to grant super-admin privileges to arbitrary accounts. A leaked or delegated read-only CI/monitoring key can therefore gain full super-admin write capability. Fixed in 1.0.13.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisPrivileges are granted, or fail to be dropped, incorrectly, so an action runs with more power than it should. An attacker who reaches that path inherits the excess privilege. The fix is least-privilege throughout, with explicit, checked transitions whenever privilege changes.
General guidance for the improper privilege management class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade grav-plugin-api to version 1.0.13 or later
- 1. Identify the Grav CMS installation running the getgrav/grav-plugin-api plugin
- 2. Check the current version of grav-plugin-api (typically in plugins/api/plugin.yaml or via Grav admin panel > Plugins > API
- 3. If version is >= 1.0.6 and <= 1.0.11, upgrade to version 1.0.13 or later
- 4. If using Composer, run: composer update getgrav/grav-plugin-api
- 5. Alternatively, download the latest version from getgrav.org or the GitHub releases page
- 6. Clear any caches after upgrade (bin/grav clear-cache)
- 7. Verify the new version is installed and test that scoped API keys now properly enforce their declared permissions
Generated from the published advisory — verify against the referenced sources before acting.
There is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $4,900. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-72833 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesThe CVE identifies a privilege escalation in Grav's API plugin where four endpoints use `isSuperAdmin()` to bypass permission scoping entirely — read-only API keys can perform write actions if the underlying account has super-admin privileges. The 8.8 CVSS is accurate, but the real exposure isn't the four controllers; it's the parallel authorization architecture that allowed this pattern to exist at all. These endpoints were almost certainly gated only by `isSuperAdmin()` when the plugin was admin-only, and `requirePermission()` was bolted on later for API key scoping. The early-return pattern isn't negligence — it's a legacy migration artifact common to systems that add capability-based authorization after identity-based gates are already entrenched. The 1.0.13 patch adds `requirePermission()` calls to the four known endpoints, which closes the immediate bypass but leaves the broader architectural problem untouched: `isSuperAdmin()` still executes as a parallel gate elsewhere in the plugin, and the underlying authorization paradigm collision — identity checks versus capability assertions — remains unresolved. More critically, the EPSS of 0.00261 measures external exploitation, not credential-valid exploitation. A read-only key minted against a super-admin account before patching is still a valid credential that can now be tested against the same system it was issued for. Organizations should treat every pre-1.0.13 scoped key on super-admin accounts as compromised infrastructure and rotate them. The plugin's authorization layer needs a structural fix — `isSuperAdmin()` should either enforce scope checks or be deprecated with architectural signals preventing future use, not patched case-by-case.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-72833 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data