Suspended Directus user can continue to use session token to access API
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2025-30351
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 8 Nov 2026, 00:33 UTC · Revision 1
Source evidence
Suspended Directus user can continue to use session token to access API
core-osv · Original sourcePublished 26 Mar 2025, 17:13 UTC
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.
osv:CVE-2025-30351
Complete source record
{
"id": "183d37f3ca9dac9b58b3b5fa187d61066594bb1aed523496d6970873e2fe1ce6",
"url": "https://osv.dev/vulnerability/CVE-2025-30351",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Suspended Directus user can continue to use session token to access API",
"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.",
"evidence": "osv:CVE-2025-30351",
"products": [],
"severity": "low",
"structured": {
"id": "CVE-2025-30351",
"aliases": [
"CVE-2025-30351",
"GHSA-56p6-qw3c-fq2g"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/directus/directus",
"type": "GIT",
"events": [
{
"introduced": "9d88df621fec13d88665b81c4335bd43b66abe4d"
},
{
"fixed": "f854746ef0a28c1208d51ab36386e3b353fd721d"
},
{
"fixed": "ef179931c55b50c110feca8404901d5633940771"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:monospace:directus:*:*:*:*:*:node.js:*:*",
"range": [
{
"introduced": "10.10.0"
},
{
"fixed": "11.5.0"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "ef179931c55b50c110feca8404901d5633940771"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v11.4.1",
"v11.4.0",
"v11.3.5",
"v11.3.4",
"v11.3.3",
"v11.3.2",
"v11.3.1",
"v11.3.0",
"v11.2.2",
"v11.2.1",
"v11.2.0",
"v11.1.2",
"v11.1.1",
"v11.1.0",
"v10.13.2",
"v11.0.2",
"v11.0.1",
"v11.0.0",
"v10.13.1",
"v10.13.0",
"v10.12.1",
"v10.11.2",
"10.11.2",
"v10.11.1",
"v10.11.0",
"v10.10.7",
"v10.10.6",
"v10.10.5",
"v10.10.4",
"v10.10.3",
"v10.10.2",
"v10.10.1",
"v10.10.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-30351.json"
}
}
],
"modified": "2026-10-28T02:30:52.234284108Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/30xxx/CVE-2025-30351.json",
"https://github.com/directus/directus/security/advisories/GHSA-56p6-qw3c-fq2g",
"https://nvd.nist.gov/vuln/detail/CVE-2025-30351",
"https://github.com/directus/directus/commit/ef179931c55b50c110feca8404901d5633940771"
],
"provider_metadata": {
"cwe_ids": [
"CWE-672"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/30xxx/CVE-2025-30351.json"
}
},
"related_cves": [
{
"value": "CVE-2025-30351",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 520997,
"published_at": "2025-03-26T17:13:42.096+00:00"
}