CVE-2025-30351

mediumpriority · track · 17EPSS 0.004 · 31 %ileEUUS

grimoire priorityP3 · Track

Exploitable?

—

no known exploitation

Likely / severe?

0.37% (31st) EPSS

CVSS 4.3 · medium

Is it mine?

6 products

Check your exposure

Who says so?

4 sources

cnnvd · enisa_euvd · nvd · osv

EPSS · scored 2026-10-27

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.

cvss

Technical severity, 0–10. One row per scoring source.

4.3

010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–medium · 3.5–4.3

v3.14.3mediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:Nprimary · NVD / NIST USexploitability 2.8 · impact 1.4

v3.13.5lowCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:Nsecondary · ENISA EU

v3.13.5lowCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:Nsecondary · security-advisories@github.comexploitability 2.1 · impact 1.4

v3.13.5lowCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:Nsecondary · OSV

v3.14mediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:Usecondary · CVSS-BT (t0sche)

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Exploitation: poc · Automatable: no · Technical Impact: partialcoordinatorcisa_ssvcUS

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-672USCWE-672US

affected products (6)

Products and version ranges known to be affected.

directus directus10.10.0, → 11.15.0enisa_euvdEU
directus directus10.10.0, → 11.5.0enisa_euvdEU
monospace directus10.10.0 → 11.5.0nvdUScpe:2.3:a:monospace:directus:*:*:*:*:*:*:*:*
npm @directus/api18.0.0 → 24.0.1osvUSpkg:npm/%40directus/api
npm @directus/types11.0.7 → 13.0.0osvUSpkg:npm/%40directus/types
npm directus10.10.0 → 11.5.0osvUSpkg:npm/directus

advisories (1)

Vendor and ecosystem advisories describing this.

GHSA-56p6-qw3c-fq2gSuspended Directus user can continue to use session token to access API2025-03-26ghsa · osvUS
### 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.

also known as (3)

Other names and identifiers for this entity.

sources

Which sources assert this record, and when.

cnnvd enisa_euvd nvd osv NVD CVE.org MITRE

published 2025-03-26modified 2026-06-17

references (8)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan