Advisory

GHSA-56p6-qw3c-fq2g

Also known as: CVE-2025-30351

Summary

Suspended Directus user can continue to use session token to access API

Details

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.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2025-03-26 18:30 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

directus

npm · All systems

Affected

  • introduced 10.10.0, fixed 11.5.0 (semver)

Fixed versions

11.5.0

Fix

@directus/api

npm · All systems

Affected

  • introduced 18.0.0, fixed 24.0.1 (semver)

Fixed versions

24.0.1

Fix

@directus/types

npm · All systems

Affected

  • introduced 11.0.7, fixed 13.0.0 (semver)

Fixed versions

13.0.0

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences