CVE-2025-30351: Suspended Directus user can continue to use session token to access API
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.
Published Mar 26, 2025 · Updated Jun 9, 2025
Affected packages
directus
- Ecosystem
- npm
- Affected
- >= 10.10.0, < 11.5.0
- Fixed in
- 11.5.0
- Check
npm ls directus
@directus/api
- Ecosystem
- npm
- Affected
- >= 18.0.0, < 24.0.1
- Fixed in
- 24.0.1
- Check
npm ls @directus/api
@directus/types
- Ecosystem
- npm
- Affected
- >= 11.0.7, < 13.0.0
- Fixed in
- 13.0.0
- Check
npm ls @directus/types
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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/refreshcall, as that invalidates the session - Access the API with
Authorization: Bearer <token>
Impact
This weakens the security of suspending users.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-129239
Directus: Share update allows reassigning user_created and role
medium6.5Nov 16, 2026CVE-2026-61835
Directus: SSRF Protection Bypass via 0.0.0.0 in File Import
high7.7Jul 20, 2026CVE-2026-61836
Directus: Authorization-dependent response served from unsegmented cache key
high8.6Jul 20, 2026CVE-2026-35408
Directus: Missing Cross-Origin Opener Policy
high8.7Apr 4, 2026CVE-2026-35409
Directus: SSRF Protection Bypass via IPv4-Mapped IPv6 Addresses in File Import
high7.7Apr 4, 2026CVE-2026-35410
Directus: Open Redirect via Parser Bypass in OAuth2/SAML Authentication Flow
medium6.1Apr 4, 2026
