Vulnerability in Directus
CVE-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 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.
EPSS: 0.003 (26.2th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 3.5 (Low). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N.
Affected products
- Directus — versions >= 10.10.0, < 11.5.0
- Monospace Directus
Weakness classification (CWE)
References
- security-advisories@github.com (x_refsource_CONFIRM, Exploit, Vendor Advisory)
- security-advisories@github.com (Patch, x_refsource_MISC)
Frequently asked questions
- What is CVE-2025-30351?
- CVE-2025-30351 is a low-severity vulnerability in Directus, classified under Operation on a Resource after Expiration or Release. CVSS score: 3.5/10. Published 2025-03-26.
- How severe is CVE-2025-30351?
- Low severity. CVSS v3 base score is 3.5 out of 10.