# Grav: Missing admin.super guard on core group blueprint access field allows admin.users operator to escalate to super-admin

Advisory record · `GHSA-xhfv-7758-r9hx`

- **Identifiers:** `GHSA-xhfv-7758-r9hx` · `CVE-2026-75837` · `PKSA-dzhx-7r7k-p6cx`
- **State:** Confirmed
- **Severity:** CVSS 9.3 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-269](https://cwe.mitre.org/data/definitions/269.html) · [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Privilege escalation](https://agentprime.io/advisories/tag/privilege-escalation.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 17 Sept 2026
- **Updated:** 17 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 Sept 2026, 20:45 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.3: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `getgrav/grav` (Packagist): affected `<2.0.14`; fixed in `2.0.14`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Grav (getgrav/grav) versions before 2.0.14 do not protect the access field of the core group blueprint, so an authenticated admin with admin.users update permission but not admin.super can grant admin.super to a group. Members of that group then gain super-admin rights, which the source says can lead to code execution through the scheduler. Upgrade to version 2.0.14, the fixed release listed.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.3 Critical, CVSS 4.0: `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`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0049, the 42nd percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 13:55 UTC: First seen by agentprime
- 31 Oct 2026, 13:55 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-xhfv-7758-r9hx)

## Sources

- [GitHub Advisory Database: GHSA-xhfv-7758-r9hx](https://github.com/advisories/GHSA-xhfv-7758-r9hx)
- [OSV: GHSA-xhfv-7758-r9hx](https://osv.dev/vulnerability/GHSA-xhfv-7758-r9hx)
- <https://github.com/getgrav/grav/security/advisories/GHSA-xhfv-7758-r9hx>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-75837>
- <https://github.com/getgrav/grav>
- <https://www.vulncheck.com/advisories/grav-before-privilege-escalation-via-group-access-field>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-xhfv-7758-r9hx>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xhfv-7758-r9hx/>. Everything for agents: <https://agentprime.io/llms.txt>.