API Key Scope Bypass in Grav Reports Plugin

The getgrav/grav-plugin-api plugin before 1.0.13 contains an API-key scope cap bypass in the POST /reports/twig-content/allowlist endpoint (ReportsController). The endpoint enforces requirePermission('api.config.write') followed by a bare isSuperAdmin() check instead of requireSuper(). Because isSuperAdmin() reads access.api.super directly and never consults api_key_scopes, a least-privilege API key scoped to api.config.write minted on a super account passes the gate, allowing an attacker to append attacker-chosen tokens to the security.twig_sandbox allowlist (persisted to user/config/security.yaml). Widening the allowlist turns any subsequent Twig-in-content render into an SSTI/RCE sink.

Casky was already ahead

This CVE exploits attack patterns that Casky's 283matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

The getgrav/grav-plugin-api plugin before version 1.0.13 contains a critical authorization flaw in the POST /reports/twig-content/allowlist endpoint. The vulnerability stems from improper permission validation where the endpoint checks isSuperAdmin() directly instead of enforcing requireSuper(), which fails to validate API key scope restrictions. This allows attackers with a least-privilege API key scoped only to 'api.config.write' to bypass authorization controls and access privileged functionality intended for super administrators. Organizations using this plugin are at risk of unauthorized configuration modifications and potential system compromise, particularly those relying on API keys with restricted scopes for automation and third-party integrations.

Casky's 754 security skills—powered by Claude AI with extended reasoning—correlate this vulnerability to MITRE ATT&CK Privilege Escalation (TA0004) and Credential Access (TA0006) techniques. Practitioners using Casky would identify attack patterns including: improper permission enforcement (CWE-862), detection of authorization bypass attempts where limited-scope credentials access restricted endpoints, suspicious API calls to /reports/twig-content/allowlist from accounts with mismatched privilege levels, and evidence of scope-constraint circumvention in API key validation logs. The platform's skill-based detection would flag the disconnect between declared API key permissions and actual endpoint access, enabling security teams to catch this exploitation pattern before attackers escalate privileges or exfiltrate sensitive configuration data.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

283 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-72825.

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

Access with Stolen Session Cookie

cryptography · low

Run

MITRE ATT&CK Techniques

TA0004 TA0006

Investigate the attack patterns behind CVE-2026-72825

Casky has 283 skills that investigate the attack patterns behind CVE-2026-72825. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn