CVE-2025-30351
CVE-2025-30351 · Suspended Directus user can continue to use session token to access API
This page contains facts from public vulnerability sources. Check the original advisory before updating.
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.
CVSS 3.5 · Low · EPSS 0.4% · Fix available
- Published
- Updated
Stack: node
Affected products and versions
directus
- Versions
- >= 10.10.0, < 11.5.0: Affected
No fix published
directus npm
- Affected ranges
- SEMVER: ≥ 10.10.0, < 11.5.0
Update to 11.5.0
@directus/api npm
- Affected ranges
- SEMVER: ≥ 18.0.0, < 24.0.1
Update to 24.0.1
@directus/types npm
- Affected ranges
- SEMVER: ≥ 11.0.7, < 13.0.0
Update to 13.0.0