CVE-2025-30351: Directus Suspended Directus User Can Continue Vulnerability
LOWCVE-2025-30351 is a LOW (CVSS 3.5) suspended directus user can continue vulnerability (CWE-672: Operation on a Resource after Expiration or Release) affecting Directus libraries in the npm ecosystem. The issue involves suspended directus user can continue to use session token to access api. Remediation is available by upgrading affected packages to version 11.5.0, 24.0.1, 13.0.0.
CVE-2025-30351 at a Glance
Security Impact
CVSS: 3.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N).
How to Fix CVE-2025-30351
To remediate this vulnerability, upgrade all affected Directus dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install directus@11.5.0
npm install @directus/api@24.0.1
npm install @directus/types@13.0.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls directus
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2025-30351, inspect your project dependencies using npm:
npm ls directus
Analyze the terminal output to locate any version of Directus in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 11.5.0), your application is affected.
Note: The npm ls directus command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-672: Operation on a Resource after Expiration or Release, where the product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked. In Directus, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-30351 Affected Directus Versions
3 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
directus
|
npm |
≥ 10.10.0
< 11.5.0
|
11.5.0
|
|
@directus/api
|
npm |
≥ 18.0.0
< 24.0.1
|
24.0.1
|
|
@directus/types
|
npm |
≥ 11.0.7
< 13.0.0
|
13.0.0
|
References
Frequently Asked Questions
What is CVE-2025-30351?
Which Directus versions are affected?
What version fixes CVE-2025-30351?
Is directus affected?
Is @directus/api affected?
What is the CVSS score of CVE-2025-30351?
What CWE is associated with CVE-2025-30351?
How can I check npm dependencies for CVE-2025-30351?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-56p6-qw3c-fq2g",
"modified" : "2025-06-09T18:12:09Z",
"published" : "2025-03-26T18:30:43Z",
"aliases" : [ "CVE-2025-30351" ],
"summary" : "Suspended Directus user can continue to use session token to access API",
"details" : "### Summary\nSince 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.\n\n### Details\nThere 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.\n\n### PoC\n* Create an active user\n* Log in with that user and note the session cookie\n* Suspend the user (and don't trigger an `/auth/refresh` call, as that invalidates the session\n* Access the API with `Authorization: Bearer <token>`\n\n### Impact\nThis weakens the security of suspending users.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "directus"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "10.10.0"
}, {
"fixed" : "11.5.0"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "@directus/api"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "18.0.0"
}, {
"fixed" : "24.0.1"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "@directus/types"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "11.0.7"
}, {
"fixed" : "13.0.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/directus/directus/security/advisories/GHSA-56p6-qw3c-fq2g"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-30351"
}, {
"type" : "WEB",
"url" : "https://github.com/directus/directus/commit/ef179931c55b50c110feca8404901d5633940771"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/directus/directus"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-672" ],
"severity" : "LOW",
"github_reviewed" : true,
"github_reviewed_at" : "2025-03-26T18:30:43Z",
"nvd_published_at" : "2025-03-26T18:15:26Z"
}
}