Vulnerability · Published Mar 26, 2025 · Assigned by GitHub_M
CVE-2025-30351Suspended Directus user can continue to use session token to access API
Low 3.5
In plain English
A low-severity security flaw in directus from directus. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 31% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| npm | @directus/api | 24.0.1 | GHSA-56p6-qw3c-fq2g |
| npm | @directus/types | 13.0.0 | GHSA-56p6-qw3c-fq2g |
| npm | directus | 11.5.0 | GHSA-56p6-qw3c-fq2g |
Affected products (as reported)
Weakness: CWE-672 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N