Security readout for executives and security teams
Plain-English summary
A limited API key tied to a Grav super administrator can bypass its intended scope and create or promote another full super administrator. This could give an attacker complete administrative control, including access to sensitive data, configuration changes, and service disruption.
Executive priority
Treat affected, API-accessible deployments as urgent because a qualifying limited key can become full administrative control. Prioritize version verification, upgrading, credential rotation, and privileged-account review. Lower priority only when the API plugin is absent, already fixed, or no qualifying keys exist.
Technical view
Grav API plugin versions before 1.0.13 incompletely enforce API-key scope limits in UsersController create() and update(). Although api.users.write is checked, the super-administrator decision reads access.api.super without applying the key’s scopes, permitting unauthorized super privileges through direct access settings or super-granting groups.
Likely exposure
Exposure is limited to Grav deployments running the API plugin before 1.0.13 where a key with api.users.write was issued from a super account. Internet-accessible API endpoints increase practical risk. The supplied sources do not establish whether the plugin or qualifying keys are commonly deployed.
Exploitation context
Exploitation requires an existing api.users.write-scoped key associated with a super account; it is not described as unauthenticated. Successful abuse can produce an unrestricted administrator account. The CVE is not listed as KEV in the supplied bundle, and no cited source establishes active exploitation.
Researcher notes
The authorization flaw is CWE-269 and has CVSS 3.1 score 8.8: network reachable, low complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impact. Evidence does not establish public exploit availability, observed attacks, deployment prevalence, or persistence mechanisms.
Mitigation direction
- Upgrade the Grav API plugin to version 1.0.13 or later, following vendor guidance.
- Revoke or rotate API keys issued from super-administrator accounts.
- Review and remove unauthorized super accounts, privileged groups, and access.api.super assignments.
- Restrict API access at the network layer until affected deployments are updated.
Validation and detection
- Inventory Grav deployments and confirm the installed API plugin version.
- Identify api.users.write keys originating from super-administrator accounts.
- Audit recent user creation, user updates, privileged group assignments, and super-access changes.
- Confirm restricted keys cannot grant access.api.super or super-granting groups 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-269: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookupCVE-2026-72829 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-jrm3-jpp7-3gmx)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: Grav before 1.0.13 API Key Scope Bypass via UsersControllerCVE 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.
Improper Privilege Management
Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.