CVE-2025-30351VulnerabilityPublished 26 Mar 2025Updated 9 Jun 2025

CVE-2025-30351: directus · Operation on a Resource after Expiration or Release

Affects directusSource CVE Database V5

Not known to be exploited · CVSS 3.5 Low · fixed in 11.5.0 : update directus when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

3.5Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 11.5.0

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Mar 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubdirectus/directus`pkg:github/directus/directus`Other threats	Affected =10.10.0 =11.5.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should upgrade Directus to version 11.5.0 or later, where the vulnerability is patched by adding a verification step to ensure users are active before allowing API access. Until the upgrade can be performed, organizations should implement compensating controls such as: 1) Immediately invalidating all active session tokens for users upon suspension, if supported by the platform or via custom scripting; 2) Monitoring API access logs for unusual activity from suspended accounts; 3) Reducing token lifetime to minimize the window of exposure; 4) Enforcing stricter session management policies, including manual token revocation; 5) Restricting API access through network-level controls or API gateways that can enforce additional authentication checks. Regular audits of user status and session validity should be conducted to ensure suspended users do not retain access. Finally, organizations should review their incident response plans to include scenarios involving session token misuse.

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.

Impact

For European organizations using Directus within the affected version range, this vulnerability could lead to unauthorized API access by users who have been suspended, potentially violating internal access control policies. While the impact on confidentiality and integrity is limited, the continued access could allow suspended users to view sensitive data or perform read operations that should have been revoked. This could result in compliance issues, especially under GDPR, where strict access controls and data protection are mandated. Additionally, organizations relying on Directus for critical data management might face operational risks if suspended users retain access longer than intended. The low CVSS score reflects the limited severity, but the risk is non-negligible in environments with strict user lifecycle management and regulatory compliance requirements. Since no known exploits are reported in the wild, the immediate threat level is low, but the vulnerability should be addressed promptly to prevent potential misuse.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Jul 2025, 22:19 UTC

WeaknessesCWE-672

Technical details

References

Community reviews

Related threats