Continued API access via unrevoked session tokens
Published Mar 26, 2025 · Updated Jun 9, 2025
Improper session invalidation in Directus allows remote authenticated users to retain API access after their accounts are suspended. In versions 10.10.0 through versions before 11.5.0, session-token verification omits an active-status check, and suspension does not revoke existing sessions. Exploitation requires a token issued while the account was active; it remains usable with that account's permissions until expiration.
Summary
What happened
Improper session invalidation in Directus allows remote authenticated users to retain API access after their accounts are suspended. In versions 10.10.0 through versions before 11.5.0, session-token verification omits an active-status check, and suspension does not revoke existing sessions. Exploitation requires a token issued while the account was active; it remains usable with that account's permissions until expiration.
The record
- CVE
- CVE-2025-30351
- Published
- Mar 26, 2025
- Updated
- Jun 9, 2025
- Vendor
- Directus
- Product
- Directus
- Classifications
- CWE-672, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 26, 2025CVE publishedPublication date reported by the CVE source.
- Jun 9, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 10.10.0, < 11.5.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor session-token reproduction procedureproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo