CyberRota Analysis
AI-GeneratedDirectus versions prior to 12.0.0 are vulnerable due to a flaw in the response caching mechanism, which allows unauthorized users to access cached data by omitting critical authorization context. This can lead to exposure of sensitive information, as different users or anonymous clients may receive permission-filtered responses without proper access checks. Organizations using Directus for managing SQL databases should prioritize upgrading to version 12.0.0 to mitigate this high-severity risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Directus is a real-time API and App dashboard for managing SQL database content. Prior to 12.0.0, when response caching is enabled, the cache-key derivation in api/src/utils/get-cache-key.ts includes version, path, query, and accountability.user but omits authorization context such as share, role, roles, admin, app, and policies. Directus share tokens and anonymous requests can both reduce to user null, so different shares or anonymous clients requesting the same URL and query can receive a permission-filtered cached response without permission re-evaluation. This issue is fixed in version 12.0.0.
Related CVEs
Other vulnerabilities affecting the same vendor(s)