Security readout for executives and security teams
Plain-English summary
A flaw in the Grav API plugin can let a scoped API key access page-permission controls outside its intended limits. This could expose or possibly change sensitive authorization settings. The reported write-time impact remains unconfirmed, but the potential consequences and 9.3 CVSS score justify urgent attention.
Executive priority
Treat as an urgent patching and access-review item, especially where the API is network-accessible or scoped keys are widely distributed. Prioritize affected internet-facing or high-value Grav deployments. Avoid claiming compromise without supporting logs because exploitation and persistent unauthorized writes are not confirmed.
Technical view
Before version 1.0.18, BlueprintController.injectSecurityTab() uses raw isSuperAdmin() and hasPermission() checks without request context, preventing enforcement of scopeAllows(). Consequently, scoped API keys may reach security and permissions blueprint fields beyond their authorized scope. The reporter did not fully confirm that unauthorized changes persist end to end.
Likely exposure
Potentially exposed systems are Grav installations running the Grav API plugin before 1.0.18 and using scoped API keys. Practical risk depends on API reachability, possession of a scoped key, and whether the affected permission fields can be successfully written.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the provided bundle. Abuse requires a scoped API key, but the affected authorization decision may treat that key as more privileged than intended. End-to-end unauthorized modification remains unconfirmed.
Researcher notes
The defect is an authorization-capability mismatch classified as CWE-863. The missing request parameter prevents scope-aware permission evaluation in injectSecurityTab(). Researchers should distinguish unauthorized blueprint visibility from durable permission modification; the supplied evidence supports the former more clearly than the latter.
Mitigation direction
- Upgrade the Grav API plugin to version 1.0.18 or later.
- Review vendor guidance before applying changes in production.
- Rotate scoped API keys that may have been exposed or misused.
- Restrict API accessibility until affected installations are updated.
Validation and detection
- Inventory Grav API plugin versions and identify installations earlier than 1.0.18.
- Confirm scoped keys cannot access permission fields outside their assigned scope.
- Review API and administrative logs for unexpected permission-field access or changes.
- Verify sensitive page permissions against approved configuration after updating.
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-863: 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 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-80204 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
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
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:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N2.82.5VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
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-mcx6-4rvg-7r8v)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: Grav before 1.0.18 Authentication Bypass via Scoped API KeyCVE 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.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.