# CVE-2026-109320: Grav API Plugin before 1.0.36 Disabled Account Session Access Bypass

> Disabled Grav API plugin users can retain access via existing sessions, bypassing account revocation controls.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-7qfj-82q8-frw6, GHSA-wcc2-xcpr-vc5h

## What is CVE-2026-109320?

CVE-2026-109320 is a medium-severity authentication bypass vulnerability in getgrav grav-plugin-api, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Grav API plugin (grav-plugin-api) before 1.0.36 contains an improper session validation vulnerability that allows disabled accounts to keep API access, because SessionAuthenticator does not enforce account state. Disabled users can reuse an already authorized browser or remember-me session to call API endpoints until expiry, defeating operator revocation.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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


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

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

## Is CVE-2026-109320 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109320 is a medium-severity authentication bypass vulnerability in getgrav grav-plugin-api, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109320 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-109320/ (Markdown: https://insights.sbomify.com/CVE-2026-109320/index.md)
```

## Sources

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

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