CVE-2026-80204

Grav before 1.0.18 Authentication Bypass via Scoped API Key

Published Aug 26, 2026 CVSS 4.0 · 9.3 Critical EPSS < 1% KEV · Not listed
Description
The Grav API plugin (getgrav/grav-plugin-api) before 1.0.18 does not apply the API-key scope cap in the injectSecurityTab() function of BlueprintController when deciding whether a page's security/permissions blueprint section is editable. Because the function performs raw isSuperAdmin()/hasPermission() checks without a request parameter, it cannot enforce scopeAllows(). A caller holding a scoped API key may therefore see (and potentially edit) page permission fields beyond the scope granted to the key. The end-to-end write-time impact was not fully confirmed by the reporter.

Analysis

AI-generated

Technical impact

The Grav CMS plugin 'grav-plugin-api' contains a flaw where the API-key scope check is not applied during permission editing. An attacker who holds a scoped API key could view and potentially modify permission fields for pages beyond the key’s intended scope. This could allow unauthorized changes to access controls, enabling further privilege escalation or content tampering within the site.

Affected Systems

Affected are installations of Grav CMS running any version prior to 1.0.18 that use the grav-plugin-api. When the plugin is active, the vulnerability can be triggered from any authenticated API endpoint that processes page security blueprints. The vendor listed is getgrav, with product Grav, and the fix is available in release 1.0.18.

Risk and Exploitability

The CVSS score of 9.3 places this issue in the ‘Critical’ range, demonstrating a significant potential impact. The EPSS score is not available, so the exact likelihood of exploitation in the wild is unknown, but the high severity suggests attackers could attempt exploitation soon. The vulnerability is not listed in the CISA KEV catalog. The most likely attack vector involves an attacker sending HTTP requests to Grav’s API endpoints using a scoped API key, leveraging the unbounded permission editing capability. Because the flaw bypasses permission checks at runtime, exploitation requires only the presence of a valid API key and network access to the API.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Grav CMS to version 1.0.18 or later, which includes the fix for the scoped API key enforcement in the API plugin.
  • Regenerate any existing API keys after patch to ensure key scopes are correctly applied and avoid using compromised or improperly scoped keys.
  • Audit page permission configurations to identify any changes made during the vulnerable period and reset such changes to intended permissions.

Generated by OpenCVE AI on August 26, 2026 at 11:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description The Grav API plugin (getgrav/grav-plugin-api) before 1.0.18 does not apply the API-key scope cap in the injectSecurityTab() function of BlueprintController when deciding whether a page's security/permissions blueprint section is editable. Because the function performs raw isSuperAdmin()/hasPermission() checks without a request parameter, it cannot enforce scopeAllows(). A caller holding a scoped API key may therefore see (and potentially edit) page permission fields beyond the scope granted to the key. The end-to-end write-time impact was not fully confirmed by the reporter.
Title Grav before 1.0.18 Authentication Bypass via Scoped API Key
First Time appeared Getgrav
Getgrav grav
Weaknesses CWE-863
CPEs cpe:2.3:a:getgrav:grav:*:*:*:*:*:*:*:*
Vendors & Products Getgrav
Getgrav grav
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N'}

cvssV4_0

{'score': 9.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Aug 26, 2026, 12:03 PM
Reserved
Aug 25, 2026, 11:15 PM
Status
Deferred
Published
Aug 26, 2026, 11:16 AM
Modified
Sep 3, 2026, 5:15 AM