CVE-2026-72823: Missing Authorization in getgrav grav
The Grav API plugin (getgrav/grav-plugin-api) before 1.0.13 contains an API-key scope cap bypass in DemoController. Its private requireSuper() method checks isSuperAdmin() and returns early before invoking requirePermission(), so the api_key_scopes cap (enforced only in requirePermission()) is skipped. As a result, any scoped API key minted on a super account can bypass its scope restrictions when calling the baseline() and reset() operations (e.g. POST /api/v1/demo/reset), allowing it to capture the demo baseline or force a demo reset. Impact is bounded to demo-engine control and is conditional on demo mode being configured with writable resources.
AI Analysis
Technical Summary
The Grav API plugin before 1.0.13 contains an authorization bypass vulnerability in its DemoController. The requireSuper() method checks if the user is a super admin and returns early without invoking requirePermission(), which enforces API key scope restrictions. Consequently, scoped API keys created for super accounts can bypass their scope limitations when invoking baseline() and reset() operations. This flaw allows an attacker with such an API key to capture the demo baseline or force a demo reset. The vulnerability's impact is constrained to demo-engine control and depends on the demo mode being configured with writable resources.
Potential Impact
An attacker possessing a scoped API key minted on a super account can bypass API key scope restrictions for certain demo-related operations. This enables unauthorized capture of the demo baseline or forced demo resets. The impact is limited to the demo engine functionality and requires the demo mode to be active with writable resources. There is no indication of broader system compromise or data exposure beyond the demo environment.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict issuance of API keys to trusted super accounts only and consider disabling demo mode or limiting writable resources in the demo configuration to reduce risk.
CVE-2026-72823: Missing Authorization in getgrav grav
Description
The Grav API plugin (getgrav/grav-plugin-api) before 1.0.13 contains an API-key scope cap bypass in DemoController. Its private requireSuper() method checks isSuperAdmin() and returns early before invoking requirePermission(), so the api_key_scopes cap (enforced only in requirePermission()) is skipped. As a result, any scoped API key minted on a super account can bypass its scope restrictions when calling the baseline() and reset() operations (e.g. POST /api/v1/demo/reset), allowing it to capture the demo baseline or force a demo reset. Impact is bounded to demo-engine control and is conditional on demo mode being configured with writable resources.
CVSS v4.0
Score 5.3medium
Affected software
pkg:github/getgrav/grav-plugin-apiRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Grav API plugin before 1.0.13 contains an authorization bypass vulnerability in its DemoController. The requireSuper() method checks if the user is a super admin and returns early without invoking requirePermission(), which enforces API key scope restrictions. Consequently, scoped API keys created for super accounts can bypass their scope limitations when invoking baseline() and reset() operations. This flaw allows an attacker with such an API key to capture the demo baseline or force a demo reset. The vulnerability's impact is constrained to demo-engine control and depends on the demo mode being configured with writable resources.
Potential Impact
An attacker possessing a scoped API key minted on a super account can bypass API key scope restrictions for certain demo-related operations. This enables unauthorized capture of the demo baseline or forced demo resets. The impact is limited to the demo engine functionality and requires the demo mode to be active with writable resources. There is no indication of broader system compromise or data exposure beyond the demo environment.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict issuance of API keys to trusted super accounts only and consider disabling demo mode or limiting writable resources in the demo configuration to reduce risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-10T15:12:59.508Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7f0284bf8831d539fec850
Added to database: 08/14/2026, 11:56:52 UTC
Last enriched: 08/14/2026, 12:12:49 UTC
Last updated: 08/14/2026, 13:16:02 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.