CVE-2025-30351: Suspended Directus user can continue to use session token to access API

3.5 CVSS

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.

Classification

CVE ID: CVE-2025-30351

CVSS Base Severity: LOW

CVSS Base Score: 3.5

CVSS Vector: CVSS: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

Affected Products

Vendor: directus

Product: directus

Exploit Prediction Scoring System (EPSS)

EPSS Score: 0.03% (probability of being exploited)

EPSS Percentile: 7.24% (scored less or equal to compared to others)

EPSS Date: 2025-04-24 (when was this score calculated)

Stakeholder-Specific Vulnerability Categorization (SSVC)

SSVC Exploitation: poc

SSVC Technical Impact: partial

SSVC Automatable: false

References

https://nvd.nist.gov/vuln/detail/CVE-2025-30351
https://github.com/directus/directus/security/advisories/GHSA-56p6-qw3c-fq2g
https://github.com/directus/directus/commit/ef179931c55b50c110feca8404901d5633940771

Timeline