Suspended Directus user can continue to use session token to access API
cve-program · CVE-2025-30351
PublishedDirectus 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.
Read the publisher's advisoryeuvd · EUVD-2025-8232
PublishedDirectus 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.
Read the publisher's advisorynvd · CVE-2025-30351
PublishedDirectus 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.
Read the publisher's advisoryosv · GHSA-56p6-qw3c-fq2g
Published### 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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2025-30351 · CVE overview and exploitation status
cve-program · CVE-2025-30351
- https://github.com/directus/directus/security/advisories/GHSA-56p6-qw3c-fq2g
- https://github.com/directus/directus/commit/ef179931c55b50c110feca8404901d5633940771
euvd · EUVD-2025-8232
- https://github.com/directus/directus/security/advisories/GHSA-56p6-qw3c-fq2g
- https://github.com/directus/directus/commit/ef179931c55b50c110feca8404901d5633940771
nvd · CVE-2025-30351
- https://github.com/directus/directus/commit/ef179931c55b50c110feca8404901d5633940771
- https://github.com/directus/directus/security/advisories/GHSA-56p6-qw3c-fq2g
osv · GHSA-56p6-qw3c-fq2g
Related changes
Linked by CVE identifierNo related changes are available here.