CVE-2025-30351 – Directus Session Token Abuse

The following table lists the changes that have been made to the
CVE-2025-30351 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution
of a vulnerability, and for identifying the most recent changes that may
impact the vulnerability’s severity, exploitability, or other characteristics.

  • New CVE Received
    by [email protected]

    Mar. 26, 2025

    Action Type Old Value New Value
    Added 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.
    Added CVSS V3.1 AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
    Added CWE CWE-672
    Added Reference https://github.com/directus/directus/commit/ef179931c55b50c110feca8404901d5633940771
    Added Reference https://github.com/directus/directus/security/advisories/GHSA-56p6-qw3c-fq2g
  • CVE Modified
    by 134c704f-9b21-4f2e-91b3-4a467353bcc0

    Mar. 26, 2025

    Action Type Old Value New Value
    Added Reference https://github.com/directus/directus/security/advisories/GHSA-56p6-qw3c-fq2g
Share the Post:

Related Posts