Skip to content
OpenAdvisories
Low · 3.5 CVE-2025-30351 EUVD-2025-8232GHSA-56p6-qw3c-fq2g

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

Published Mar 26, 2025 · Updated Jun 9, 2025 · Assigned by GitHub_M

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.

Affected products

VendorProductAffectedFixed
directus directus >= 10.10.0, < 11.5.0 —

Affected packages

EcosystemPackageAffectedFixedRecord
npm @directus/api >= 18.0.0, < 24.0.1 24.0.1 GHSA-56p6-qw3c-fq2g
npm @directus/types >= 11.0.7, < 13.0.0 13.0.0 GHSA-56p6-qw3c-fq2g
npm directus >= 10.10.0, < 11.5.0 11.5.0 GHSA-56p6-qw3c-fq2g

References