We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.

Please see our statement on Data Privacy.

Crisp.chat (Helpdesk and Chat)

Ok

THREATINT
PUBLISHED

CVE-2025-30351

Suspended Directus user can continue to use session token to access API



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.

Reserved 2025-03-21 | Published 2025-03-26 | Updated 2025-03-26 | Assigner GitHub_M


LOW: 3.5CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N

Problem types

CWE-672: Operation on a Resource after Expiration or Release

Product status

>= 10.10.0, < 11.15.0
affected

References

github.com/...rectus/security/advisories/GHSA-56p6-qw3c-fq2g

github.com/...ommit/ef179931c55b50c110feca8404901d5633940771

cve.org (CVE-2025-30351)

nvd.nist.gov (CVE-2025-30351)

Download JSON

Share this page
https://cve.threatint.eu/CVE/CVE-2025-30351

Support options

Helpdesk Chat, Email, Knowledgebase