CVE-2025-30351: Suspended Directus user can continue to use session token to access API

Severity: medium (CVSS 4.3 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.4% probability of exploitation in the next 30 days
Public exploit or detection template: yes
Published: 2025-03-26 · updated 2026-06-17
Weakness: CWE-672

Description

Directus is a real-time API and App dashboard for managing SQL database content. Starting in version 10.10.0 and prior to version 11.5.0, a suspended user can use the token generated in session auth mode to access the API despite their status. This happens because there is a check missing in `verifySessionJWT` to verify that a user is actually still active and allowed to access the API. One can extract the session token obtained by, e.g. login in to the app while still active and then, after the user has been suspended continue to use that token until it expires. Version 11.5.0 patches the issue.

Affected products

directus: from 10.10.0 before 11.5.0 — fixed in 11.5.0

How to fix

Upgrade to a fixed version: directus 11.5.0. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2025-30351 or the next vulnerability affects your stack