CVE-2025-30351
Suspended Directus user can continue to use session token to access API
Description
### 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.
How to fix CVE-2025-30351
To remediate CVE-2025-30351, upgrade the affected package to a fixed version below.
- —upgrade to 11.5.0 or later
- —upgrade to 24.0.1 or later
- —upgrade to 13.0.0 or later
Is CVE-2025-30351 being exploited?
Low — EPSS is 0.4%, meaning exploitation activity has not been observed at scale.
Affected packages (3)
- >= 10.10.0, < 11.5.0
- >= 18.0.0, < 24.0.1
- >= 11.0.7, < 13.0.0
CVSS scores
| Source | Version | Severity | Vector |
|---|---|---|---|
| osv | CVSS 3.1 | LOW3.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N |