Security readout for executives and security teams
Plain-English summary
A flaw in the Grav API plugin can let someone with a restricted API key inherit the broader permissions of the privileged account that issued it. This may expose administrative interface metadata and user-list definitions that the key’s scope should block. The supplied record rates it critical, although the described demonstrated consequence is information disclosure.
Executive priority
Prioritize rapid inventory and upgrade, especially on internet-accessible systems using privileged-account API keys. Treat exposure as urgent because authorization boundaries can fail silently. However, communicate that the supplied evidence describes information disclosure and does not establish active exploitation or confirmed integrity and availability impact.
Technical view
Before version 1.0.14, userPassesAuthorize() in AbstractApiController.php does not evaluate the request API key’s scopes. It instead uses the issuing account’s super-admin status and ACL grants, allowing scoped keys from privileged accounts to bypass authorization checks for sidebar, menubar, widget, and users-list definitions.
Likely exposure
Exposure is most likely where the Grav API plugin is older than 1.0.14 and scoped API keys were issued from privileged or super-admin accounts. Exploitation requires a valid scoped key according to the description. The supplied PR:N CVSS vector conflicts with that authenticated-attacker requirement.
Exploitation context
The bundle reports no CISA KEV listing and provides no evidence of active exploitation. Abuse is remotely reachable and described as low complexity once an attacker possesses an affected API key. Do not treat the critical CVSS score alone as proof of exploitation in the wild.
Researcher notes
The authorization decision uses account-level super-admin and ACL grants without consulting request-specific scopes. The stated affected boundary is before 1.0.14. The CVSS 4.0 vector claims no privileges and high confidentiality, integrity, and availability impact, but the narrative requires an authenticated key and documents information disclosure; this discrepancy needs vendor clarification.
Mitigation direction
- Upgrade the Grav API plugin to version 1.0.14 or later after reviewing vendor guidance.
- Until upgraded, revoke or restrict scoped API keys issued from privileged accounts.
- Rotate potentially exposed keys and minimize issuing privileged-account API credentials.
- Review access to affected administrative metadata and user-list definition endpoints.
Validation and detection
- Inventory Grav API plugin versions and identify every installation older than 1.0.14.
- Identify scoped API keys issued from super-admin or broadly privileged accounts.
- Verify restricted keys cannot access authorize-gated metadata outside their declared scopes.
- Review available API access records for unexpected requests using affected scoped keys.
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-862: 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-75835 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:N/A:N2.81.4VulnCheckVulnerability 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
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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-p57v-xhv3-mf2w)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: Grav API Plugin before 1.0.14 Missing AuthorizationCVE 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 Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.