CVE-2025-30351
Description
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.
How to fix
- monospace directus11.5.0 or later
- directus11.5.0 or later
- @directus/api24.0.1 or later
- @directus/types13.0.0 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| monospace directus | 10.10.0 ≤ v < 11.5.0 | 11.5.0 |
| directusnpm | 10.10.0 ≤ v < 11.5.0 | 11.5.0 |
| @directus/apinpm | 18.0.0 ≤ v < 24.0.1 | 24.0.1 |
| @directus/typesnpm | 11.0.7 ≤ v < 13.0.0 | 13.0.0 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.