CVE-2025-30351
- Source
- https://cve.org/CVERecord?id=CVE-2025-30351
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-30351.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2025-30351
- Aliases
- Published
- 2025-03-26T17:13:42.096Z
- Modified
- 2026-04-10T05:24:45.849377Z
- Severity
-
- 3.5 (Low) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N CVSS Calculator
- Summary
- Suspended Directus user can continue to use session token to access API
- Details
-
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
verifySessionJWTto 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. - Database specific
{ "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/30xxx/CVE-2025-30351.json", "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-672" ] }- References
Affected packages
Git / github.com/directus/directus
Affected versions
10.*
10.11.2
v10.*
v10.10.0
v10.10.1
v10.10.2
v10.10.3
v10.10.4
v10.10.5
v10.10.6
v10.10.7
v10.11.0
v10.11.1
v10.11.2
v10.12.1
v10.13.0
v10.13.1
v10.13.2
v11.*
v11.0.0
v11.0.1
v11.0.2
v11.1.0
v11.1.1
v11.1.2
v11.2.0
v11.2.1
v11.2.2
v11.3.0
v11.3.1
v11.3.2
v11.3.3
v11.3.4
v11.3.5
v11.4.0
v11.4.1