3.5
CWE
672
EPSS
0.030%
Advisory Published
Advisory Published
Updated

CVE-2025-30351: Suspended Directus user can continue to use session token to access API

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 SoftwareAffected VersionHow to fix
npm/directus>=10.10.0<11.15.0
11.15.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2025-30351?

    CVE-2025-30351 has been classified as a high-severity vulnerability due to its potential to allow suspended users to access secured APIs.

  • How do I fix CVE-2025-30351?

    To address CVE-2025-30351, ensure the session token verification process checks the user's status before granting access.

  • What software versions are affected by CVE-2025-30351?

    CVE-2025-30351 affects directus versions between 10.10.0 and 11.15.0.

  • What is the main issue with CVE-2025-30351?

    The main issue with CVE-2025-30351 is that user status is not verified, allowing access to the API by suspended users.

  • When was CVE-2025-30351 disclosed?

    CVE-2025-30351 was disclosed in 2025 following an identification of the status verification issue within the software.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203