CVE-2025-30351
published 2025-03-26CVE-2025-30351: 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…
PriorityP423medium4.3CVSS 3.1
AVNACLPRLUINSUCLINAN
EPSS
0.34%
25.5th percentile
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
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| directus | api | >= 18.0.0 < 24.0.1 | 24.0.1 |
| directus | directus | — | — |
| directus | directus | >= 10.10.0 < 11.5.0 | 11.5.0 |
| directus | types | >= 11.0.7 < 13.0.0 | 13.0.0 |
| monospace | directus | >= 10.10.0 < 11.5.0 | 11.5.0 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Suspended Directus user can continue to use session token to access API
osv·2025-03-26
CVE-2025-30351 [LOW] Suspended Directus user can continue to use session token to access API
Suspended Directus user can continue to use session token to access API
### Summary
Since the user status is not checked when verifying a session token a suspended user can use the token generated in session auth mode to access the API despite their status.
### Details
There is a check missing in `verifySessionJWT` to verify that a user is actually still active and allowed to access the API. Right now 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.
### PoC
* Create an active user
* Log in with that user and note the session cookie
* Suspend the user (and don't trigger an `/auth/refresh` call, as that invalidates the session
* Access the API with `Authorizat
GHSA
Suspended Directus user can continue to use session token to access API
ghsa·2025-03-26
CVE-2025-30351 [LOW] CWE-672 Suspended Directus user can continue to use session token to access API
Suspended Directus user can continue to use session token to access API
### Summary
Since the user status is not checked when verifying a session token a suspended user can use the token generated in session auth mode to access the API despite their status.
### Details
There is a check missing in `verifySessionJWT` to verify that a user is actually still active and allowed to access the API. Right now 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.
### PoC
* Create an active user
* Log in with that user and note the session cookie
* Suspend the user (and don't trigger an `/auth/refresh` call, as that invalidates the session
* Access the API with `Authorizat
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2025-03-26
Published