External risk intelligence

Grav Plugin API Key Scope Bypass Allows Full Access

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-72826

The vulnerability exists in an API plugin for a web application platform. APIs are commonly deployed as internet-facing services or gateways to facilitate web functionality, making them a standard part of the external web-accessible attack surface.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability affects a plugin for the Grav content management system, potentially allowing an attacker to gain unauthorized full administrative access by exploiting a flaw in how API keys are created. The issue could enable further malicious actions, leading to significant compromise.

  • API key flaw grants excessive permissions.
  • Affects user access and system control.
  • Confirm relevance and exposure for security.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by interacting with an API endpoint that manages API keys. Initially, the attacker needs an API key with limited permissions to access the system. They can then send a request to create a new API key, but instead of specifying any access permissions, they submit an empty list. This allows them to obtain a new API key with full administrative privileges, bypassing the intended security restrictions and potentially leading to further malicious actions like remote code execution.

  • Entry point requires a minimal-scope API key.
  • Triggered by creating a new API key with empty scopes.
  • Risk of full administrative access and RCE.

Live Threat

Current exploitation, exposure, and threat context

The getgrav/grav-plugin-api plugin, when running with specific configurations, could allow an attacker to create new API keys with excessive permissions. This occurs because the plugin does not properly validate that the scopes of a newly created API key are a subset of the caller's scopes. An attacker could exploit this by leveraging an existing minimal-scope API key to mint an unscoped, full-access super key, potentially enabling further malicious actions such as altering configurations or achieving remote code execution.

  • API keys and system configuration data.
  • Via API requests to an affected plugin.
  • Potential for unauthorized access and control.

Operational Fix

Recommended remediation, mitigation, and detection steps

The getgrav/grav-plugin-api plugin's API key creation function requires immediate attention from platform or application owners. An unauthenticated attacker can exploit this flaw to escalate privileges from a limited API key to a full-access super key, potentially leading to remote code execution. The first actionable step is to inventory all instances of the affected plugin, identify business-critical deployments, and confirm the accountable owner for remediation.

  • Platform or application owners should own this issue.
  • Verify all plugin installations and network exposure.
  • Plan and coordinate urgent remediation actions.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the getgrav/grav-plugin-api plugin?

This component is an extension for the Grav content management system, which is a flat-file platform used for building websites. The plugin specifically adds API functionality, allowing external systems or services to interact with the site's data and administrative functions programmatically.

How does the scope bypass in CVE-2026-72826 work?

The vulnerability is categorized as CWE-266: Incorrect Privilege Assignment. The plugin fails to verify if a new API key's requested permissions are actually allowed by the caller's own permissions. Because it does not enforce a subset check, an attacker can define a new key with broader access than their own account should permit.

What actions trigger this API vulnerability?

An attacker needs an existing, low-privilege API key to initiate the request. The flaw is triggered when the attacker uses that key to create another new key while submitting an empty scopes array. It is important to note that simply having access to the API without an existing, valid low-privilege key does not trigger this specific logic path.

Why is this CVE considered high risk for internet-facing sites?

According to Halo Surface Signal, this API plugin is commonly deployed to support web functionality, making it a frequent component of the external attack surface. If your Grav site exposes these API endpoints to the public internet, the potential for an unauthorized actor to escalate privileges to full administrative control is significantly elevated.

What is the first step to address this plugin flaw?

Begin by inventorying all Grav installations to identify where the affected plugin is deployed. Since this vulnerability allows for the creation of super-user keys that could lead to full system compromise, prioritize checking your logs for unusual API key generation activity while you coordinate an update to a version beyond 1.0.13.

References