API Key Scope Enforcement Bypass in Grav Plugin

The getgrav/grav-plugin-api Composer package before 1.0.13 (affected <= 1.0.12) fails to enforce API key scope caps on the disable2fa endpoint. Unlike the sibling generate2fa endpoint, disable2fa authorizes the admin (non-self) path solely via ACL reads (isSuperAdmin/hasPermission) and never invokes requirePermission(), so the api_key_scopes cap is never applied. As a result, a holder of a narrow-scope API key on a super account, or a non-super account whose ACL includes api.users.write, can force-disable two-factor authentication on any non-super target account via POST /api/v1/users/{user}/2fa/disable without providing a TOTP code, facilitating account takeover.

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

CVE-2026-72822 is a critical authorization flaw in the getgrav/grav-plugin-api package (versions ≤ 1.0.12) where the disable2fa endpoint fails to enforce API key scope restrictions. Unlike its counterpart generate2fa endpoint, disable2fa skips the requirePermission() function that would validate API key capability caps, allowing attackers with narrow-scope API keys or limited write permissions to disable two-factor authentication for admin accounts. This vulnerability affects any Grav installation using the vulnerable plugin versions, particularly those managing sensitive user accounts or relying on API key segmentation for privilege separation.

Casky's 283 matched security skills leverage Claude's extended reasoning to detect the attack patterns underlying this vulnerability across MITRE ATT&CK techniques TA0004 (Privilege Escalation) and TA0006 (Credential Access). Practitioners using Casky would identify suspicious authorization bypass attempts through detection of API calls to disable2fa that lack proper scope validation, unusual two-factor authentication disablement by restricted API keys, and privilege escalation signals when low-capability credentials access admin-level endpoints. The platform's Claude-powered analysis would surface the missing requirePermission() validation check, correlate abnormal API key usage patterns against defined scopes, and flag instances where ACL-only checks bypass cryptographic capability enforcement—enabling security teams to spot exploitation attempts before compromised credentials become a full account takeover.

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-72822.

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-72822

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

Run the skill that detects this →

X Instagram LinkedIn