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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
directusnpm | >= 10.10.0, < 11.5.0 | 11.5.0 |
@directus/apinpm | >= 18.0.0, < 24.0.1 | 24.0.1 |
@directus/typesnpm | >= 11.0.7, < 13.0.0 | 13.0.0 |
Affected products
4- ghsa-coords3 versions
>= 18.0.0, < 24.0.1+ 2 more
- (no CPE)range: >= 18.0.0, < 24.0.1
- (no CPE)range: >= 11.0.7, < 13.0.0
- (no CPE)range: >= 10.10.0, < 11.5.0
Patches
Vulnerability mechanics
References
4- github.com/advisories/GHSA-56p6-qw3c-fq2gghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2025-30351ghsaADVISORY
- github.com/directus/directus/commit/ef179931c55b50c110feca8404901d5633940771ghsax_refsource_MISCWEB
- github.com/directus/directus/security/advisories/GHSA-56p6-qw3c-fq2gghsax_refsource_CONFIRMWEB
News mentions
0No linked articles in our index yet.