First published: Wed Mar 26 2025(Updated: )
### 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 `Authorization: Bearer <token>` ### Impact This weakens the security of suspending users.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
npm/directus | >=10.10.0<11.15.0 | 11.15.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-30351 has been classified as a high-severity vulnerability due to its potential to allow suspended users to access secured APIs.
To address CVE-2025-30351, ensure the session token verification process checks the user's status before granting access.
CVE-2025-30351 affects directus versions between 10.10.0 and 11.15.0.
The main issue with CVE-2025-30351 is that user status is not verified, allowing access to the API by suspended users.
CVE-2025-30351 was disclosed in 2025 following an identification of the status verification issue within the software.