# CVE-2026-109317: Grav API Plugin before 1.0.36 Privilege Escalation via Scalar Access Grants

> Delegated user managers can escalate to super-admin access by manipulating scalar grants in the Grav API Plugin.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-7ghm-8q85-6h4j, GHSA-m2rq-76vx-vv4j

## What is CVE-2026-109317?

CVE-2026-109317 is a high-severity vulnerability in getgrav grav-plugin-api, published on 12 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Grav grav-plugin-api before 1.0.36 contains a privilege escalation vulnerability that allows delegated user managers to obtain super-admin access by storing positive scalar admin or api parent grants. Attackers with api.users.write can edit account access maps or invitations so the inheriting permission resolver satisfies requireSuper checks, accessing super-only API endpoints.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-109317?


## How do I fix CVE-2026-109317?

No fix has been published for CVE-2026-109317 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-109317 being exploited?

There is no known exploitation of CVE-2026-109317 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109317 and fix it if it is affected.

What it is: CVE-2026-109317 is a high-severity vulnerability in getgrav grav-plugin-api, published on 12 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109317 in the wild and no public exploit code.

Affected product: getgrav grav-plugin-api. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-109317/ (Markdown: https://insights.sbomify.com/CVE-2026-109317/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-109317
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-109317
- OSV: https://osv.dev/vulnerability/CVE-2026-109317

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-109317/
Summaries are generated and may contain mistakes; the official description above is the record.