Vulnerability 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.
CVSS Score
LOW
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Monospace | Directus | >= 10.10.0, < 11.5.0 |
Related Weaknesses (CWE)
References
- https://github.com/directus/directus/commit/ef179931c55b50c110feca8404901d563394Patch
- https://github.com/directus/directus/security/advisories/GHSA-56p6-qw3c-fq2gExploitVendor Advisory
- https://github.com/directus/directus/security/advisories/GHSA-56p6-qw3c-fq2gExploitVendor Advisory
FAQ
What is CVE-2025-30351?
CVE-2025-30351 is a vulnerability with a CVSS score of 3.5 (LOW). 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 m...
How severe is CVE-2025-30351?
CVE-2025-30351 has been rated LOW with a CVSS base score of 3.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2025-30351?
Check the references section above for vendor advisories and patch information. Affected products include: Monospace Directus.