CVE-2025-30351 – directus

Package

Manager: npm
Name: directus
Vulnerable Version: >=10.10.0 <11.5.0

Severity

Level: Low

CVSS v3.1: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N

CVSS v4.0: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

EPSS: 0.00099 pctl0.28186

Details

Suspended Directus user can continue to use session token to access API ### Summary Since the user status is not checked when verifying a session token a suspended user can use the token generated in session auth mode to access the API despite their status. ### Details There is a check missing in `verifySessionJWT` to verify that a user is actually still active and allowed to access the API. Right now 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. ### PoC * Create an active user * Log in with that user and note the session cookie * Suspend the user (and don't trigger an `/auth/refresh` call, as that invalidates the session * Access the API with `Authorization: Bearer <token>` ### Impact This weakens the security of suspending users.

Metadata

Created: 2025-03-26T18:30:43Z
Modified: 2025-06-09T18:12:09Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/03/GHSA-56p6-qw3c-fq2g/GHSA-56p6-qw3c-fq2g.json
CWE IDs: ["CWE-672"]
Alternative ID: GHSA-56p6-qw3c-fq2g
Finding: F067
Auto approve: 1