CVE-2024-39896High· 7.5▾ TwilightDirectus Allows Single Sign-On User Enumeration
Directus Allows Single Sign-On User Enumeration
▾ Twilight zone — High severity, or a signal on a lesser flaw
Depth score41/ 100 · Moderate
impact 41.3 · likelihood 0.1 · exploitation 0
Proof of concept
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Published
Jul 8, 2024
Updated
Sep 16, 2026
CVSS
7.5
Vendor
directus
Product
directus
CWE
CWE-200
Depth score
41 · Moderate
EPSS
0.51% · p42
Platforms
—
Source
GHSA
Vector
—
EPSS history
Exploit-prediction probability, daily snapshots since Sep 16.
Timeline
Disclosure to exploitation, from the record and what we observed since indexing it.
- Published
Disclosed via GHSA
- Record revised
Last analysed / modified upstream
- EPSS first tracked
0.5%
Affected
- directus >= 9.11, < 10.13.0
Patched in
- directus 10.13.0
Full technical detail▾
Overview
Impact
When relying on SSO providers in combination with local authentication it can be possible to enumerate existing SSO users in the instance. This is possible because if an email address exists in Directus and belongs to a known SSO provider then it will throw a "helpful" error that the user belongs to another provider.
Reproduction
- Create a user using a SSO provider
[email protected]. - Try to log-in using the regular login form (or the API)
- When using a valid email address
| APP | API |
|---|---|
- When using an invalid email address
| APP | API |
|---|---|
- Using this differing error it is possible to determine whether a specific email address is present in the Directus instance as an SSO user.
Workarounds
When only using SSO for authentication then you can work around this issue by disabling local login using the following environment variable AUTH_DISABLE_DEFAULT="true"
References
Implemented as feature in https://github.com/directus/directus/pull/13184 https://owasp.org/www-project-web-security-testing-guide/v42/4-Web_Application_Security_Testing/03-Identity_Management_Testing/04-Testing_for_Account_Enumeration_and_Guessable_User_Account
Affected packages
directus >= 9.11, < 10.13.0
Remediation
Upgrade to a patched release:
directus 10.13.0
References
Related vulnerabilities
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-61835High· 7.7Directus: SSRF Protection Bypass via 0.0.0.0 in File Import
same productCVE-2026-61836High· 8.6Directus: Authorization-dependent response served from unsegmented cache key
same productCVE-2021-25122High· 7.5When responding to new h2c connection requests, Apache Tomcat versions 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41 and 8.5.0 to 8.5.61 could duplicate request headers and a limited amount of request body from one request to another meaning u…
CWE-200CVE-2022-31746Medium· 6.5Internal URLs are protected by a secret UUID key, which could have been leaked to web page through the Referrer header
CWE-200CVE-2026-13697High· 7.4undici vulnerable to cross-user information disclosure and parse-time crash via degenerate private cache directives
CWE-200CVE-2026-45623High· 7.5postcss: PostCSS: Information disclosure and denial of service via crafted CSS input (CVE-2026-45623)
CWE-200
#ghsa#npm