CVE-2025-30351

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>

This weakens the security of suspending users.

CVE-2025-30351 has a CVSS score of 3.5 (Low). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (11.5.0, 24.0.1, 13.0.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-30351? CVE-2025-30351 is a low-severity security vulnerability in directus (npm), affecting versions >= 10.10.0, < 11.5.0. It is fixed in 11.5.0, 24.0.1, 13.0.0.
2. How severe is CVE-2025-30351? CVE-2025-30351 has a CVSS score of 3.5 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2025-30351?
   • directus (npm) (versions >= 10.10.0, < 11.5.0)
   • @directus/api (npm) (versions >= 18.0.0, < 24.0.1)
   • @directus/types (npm) (versions >= 11.0.7, < 13.0.0)
4. Is there a fix for CVE-2025-30351? Yes. CVE-2025-30351 is fixed in 11.5.0, 24.0.1, 13.0.0. Upgrade to this version or later.
5. Is CVE-2025-30351 exploitable, and should I be worried? Whether CVE-2025-30351 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-30351 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-30351?
   • Upgrade directus to 11.5.0 or later
   • Upgrade @directus/api to 24.0.1 or later
   • Upgrade @directus/types to 13.0.0 or later