Quick answers
- Is CVE-2026-80204 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-80204 being exploited in the wild.
- How severe is CVE-2026-80204?
- Medium severity, with a CVSS score of 5.4, published 26 August 2026.
- Which products and versions are affected?
- Grav API Plugin before 1.0.18.
- Is there a fix for CVE-2026-80204?
- A patch was published on 2026-08-26: version 1.0.18 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-80204 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-80204?
- Check whether you run Grav API Plugin at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authorization bypass (CWE-863) in the injectSecurityTab() function of BlueprintController within the Grav API plugin. The function uses raw isSuperAdmin() and hasPermission() checks without a request parameter, preventing it from enforcing the scopeAllows() scope cap that is consistently applied elsewhere in the codebase. An attacker holding a scoped API key can request the page blueprint, which will incorrectly expose and permit editing of security/permissions fields beyond the scope granted to the key. The reporter confirmed the information disclosure aspect (revealing full account permissions rather than scoped key limits) but noted that end-to-end write impact depends on whether the blueprint field presence gates write-time enforcement, which was not fully traced. The fix is to thread the request object into injectSecurityTab() to enable proper scope enforcement, matching the established pattern used in hasPermissionWithinScope().
Affected products
- Grav API plugin before 1.0.18
Timeline
- 2026-08-26: disclosed
- 2026-08-26: patched: version 1.0.18