{"uuid": "36cc02c0-de30-48e4-a66d-ced526a08b09", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-30351", "type": "seen", "source": "https://t.me/cvedetector/21207", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-30351 - Directus Session Token Abuse\", \n  \"Content\": \"CVE ID : CVE-2025-30351 \nPublished : March 26, 2025, 6:15 p.m. | 31\u00a0minutes ago \nDescription : 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. \nSeverity: 3.5 | LOW \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"26 Mar 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-26T20:34:55.000000Z"}