Skip to content
Fencer Vulns
low 3.5

CVE-2025-30351 json

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

published 2025-03-26 19 mo ago modified 2026-09-10 1 mo ago also EUVD-2025-8232 , GHSA-56p6-qw3c-fq2g

cvss
3.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm directus 11.5.0
  • npm @directus/api 24.0.1
  • npm @directus/types 13.0.0
  • monospace directus 11.5.0
  • rangerstudio directus 11.5.0

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
19 mo ago

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/directus/directus/security/advisories/GHSA-56p6-qw3c-fq2g referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 3.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
GitHub 3.1 3.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm directus
>=10.10.0, <11.5.0
11.5.0
npm @directus/api
>=18.0.0, <24.0.1
24.0.1
npm @directus/types
>=11.0.7, <13.0.0
13.0.0

Affected products

  • directus directus

Classification

Weakness
  • CWE-672 Operation on a Resource after Expiration or Release

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.