Security readout for executives and security teams
Plain-English summary
A user holding certain API keys can switch off two-factor authentication for other non-super administrator accounts, even when the key’s intended scope should forbid that action. This weakens a major account-protection control and could support account takeover without requiring the victim’s one-time code.
Executive priority
Treat as a high-priority identity-security issue. Upgrade promptly, then investigate whether privileged API keys accessed the 2FA-disable endpoint. Internet-facing or widely integrated deployments deserve accelerated handling because disabling 2FA can remove a key barrier to administrator account takeover.
Technical view
getgrav/grav-plugin-api through 1.0.12 does not apply api_key_scopes caps to POST /api/v1/users/{user}/2fa/disable. The non-self authorization path checks account ACLs but omits requirePermission(), unlike generate2fa. A narrow-scope key for a super account, or a key for an account with api.users.write, can therefore disable 2FA for any non-super target.
Likely exposure
Exposure requires an affected plugin version, a reachable API endpoint, and a usable API key tied to a super account or an account with api.users.write. Risk is greater where API keys are broadly distributed, insufficiently protected, or expected to be constrained by narrow scopes.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation requires low privileges rather than anonymous access, but it is remotely reachable, low complexity, requires no victim interaction, and may enable subsequent account takeover.
Researcher notes
The security failure is an authorization inconsistency: ACL eligibility is checked, but API-key scope constraints are skipped because requirePermission() is not called. The affected action targets non-super accounts and does not require a TOTP code. Available evidence supports the bypass mechanics and affected versions, but not observed exploitation.
Mitigation direction
- Upgrade getgrav/grav-plugin-api to version 1.0.13 or later.
- Restrict access to the affected API while upgrading.
- Review and revoke unnecessary API keys associated with super accounts or api.users.write.
- Re-enable 2FA for accounts where it was unexpectedly disabled.
- Check vendor guidance for any additional remediation or release-specific requirements.
Validation and detection
- Confirm the installed grav-plugin-api Composer package version is 1.0.13 or later.
- Inventory API keys associated with super accounts and accounts granted api.users.write.
- Review logs for unexpected requests to user 2FA disable endpoints.
- Identify non-super accounts with unexplained 2FA configuration changes.
- Verify intended API scope restrictions are enforced after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-72822 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-22p9-6fh4-mmf2)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: Grav before 1.0.13 Authentication Bypass via disable2faCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.