Is CVE-2026-109320 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-109320 being exploited in the wild.

How severe is CVE-2026-109320?

Medium severity, with a CVSS score of 5.4, published 12 October 2026.

Is there a fix for CVE-2026-109320?

Yes: fixed in 1.0.36. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-109320 attacked?

It is attacked over the network.

Am I affected by CVE-2026-109320?

Check whether you run Grav API Plugin at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-109320: Grav API plugin session validation bypass in disabled accounts

CVE-2026-109320 · Severity: medium · CVSS 5.4 · Published 2026-10-12

The Grav API plugin processes requests through session-based authentication but fails to check whether a user account has been disabled. An attacker with an existing valid session can continue making API requests even after an administrator disables their account, until the session naturally expires. This defeats the organization's ability to immediately revoke API access for terminated or compromised accounts.

Technologies: Grav API Plugin. Vendors: Grav.

Quick answers

Is CVE-2026-109320 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-109320 being exploited in the wild.
How severe is CVE-2026-109320?: Medium severity, with a CVSS score of 5.4, published 12 October 2026.
Which products and versions are affected?: Grav API Plugin before 1.0.36.
Is there a fix for CVE-2026-109320?: Yes: fixed in 1.0.36. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-109320 attacked?: It is attacked over the network.
Am I affected by CVE-2026-109320?: Check whether you run Grav API Plugin at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 1.0.36

Technical details

The SessionAuthenticator component accepts serialized session users without verifying account enabled/disabled state, whereas the API-key and JWT authenticators correctly enforce such checks. An attacker who previously authenticated and established a browser or remember-me session can reuse it to call API endpoints with their original permissions after account disablement. The vulnerability requires prior authentication and a valid session; a fix shipped in version 1.0.36 validates account state on each request.

Affected products

Grav API plugin before 1.0.36

Timeline

2026-09-23: disclosed
2026-10-12: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.