CVE-2025-30351 Suspended Directus user can continue to use session token to access API
Suspended Directus users can retain API access using existing session tokens due to missing status verification, allowing unauthorized data access.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2025-30351?
CVE-2025-30351 is a low-severity authentication bypass vulnerability in Monospace Directus, published on 26 Mar 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official 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.
Weakness: CWE-672
Which versions are affected by CVE-2025-30351?
6 open source packages ship an affected version, including @directus/api, @directus/types and directus. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
@directus/api npm | From 18.0.0 | 24.0.1 |
@directus/api npm | From 18.0.0 | 24.0.1 |
@directus/types npm | From 11.0.7 | 13.0.0 |
@directus/types npm | From 11.0.7 | 13.0.0 |
directus npm | From 10.10.0 | 11.5.0 |
directus npm | From 10.10.0 | 11.5.0 |
Products include Monospace Directus.
How do I fix CVE-2025-30351?
Upgrade @directus/api to 24.0.1 or later.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2025-30351 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-30351 exists.
Other vulnerabilities in Monospace Directus
- CVE-2022-26969 Insecure default value for CORS configuration
- CVE-2025-55746 Directus allows unauthenticated file upload and file modification due to lacking input sanitization
- CVE-2026-35408 Directus is Missing Cross-Origin Opener Policy
- CVE-2026-61836 Directus: Authorization-dependent response served from unsegmented cache key
- CVE-2025-30353 Directus's webhook trigger flows can leak sensitive data
Sources
Also known as GHSA-56p6-qw3c-fq2g.