{"answers":{"affected":"2 open source packages ship an affected version, including directus. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39896 exists.","fix":"Upgrade directus to 10.13.0 or later.","what":"CVE-2024-39896 is a high-severity vulnerability in Monospace Directus, published on 8 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-39896 and fix it if it is affected.\n\nWhat it is: CVE-2024-39896 is a high-severity vulnerability in Monospace Directus, published on 8 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39896 exists.\n\nAffected packages and fixed versions:\n- directus (npm): affected from 9.11; fixed in 10.13.0\n- directus (npm): affected from 9.11; fixed in 10.13.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-39896/ (Markdown: https://insights.sbomify.com/CVE-2024-39896/index.md)","id":"CVE-2024-39896","markdown":"https://insights.sbomify.com/CVE-2024-39896/index.md","name":"CVE-2024-39896","record":{"aliases":["GHSA-jgf4-vwc3-r46v"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Directus API dashboard","requires_auth":"none","summary":"Attackers can enumerate existing SSO users by observing specific error messages when attempting local authentication with SSO-linked emails.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"directus","vendor":"monospace"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Directus allows SSO User Enumeration","id":"CVE-2024-39896","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"monospace:directus","products":["monospace:directus"],"type":"information_disclosure","year":"2024"},"n_packages":2,"n_references":2,"next":{"headline":"Cache driver GetBlob() allows read access to any blob without access control check","id":"CVE-2024-39897"},"packages":[{"ecosystem":"npm","fixed":["10.13.0"],"introduced":["9.11"],"last_affected":[],"package":"directus","purl":null,"source":"GHSA-jgf4-vwc3-r46v"},{"ecosystem":"npm","fixed":["10.13.0"],"introduced":["9.11"],"last_affected":[],"package":"directus","purl":"pkg:npm/directus","source":"GHSA-jgf4-vwc3-r46v"}],"prev":{"headline":"Directus GraphQL Field Duplication Denial of Service (DoS)","id":"CVE-2024-39895"},"products":["directus"],"published":"2024-07-08","related":[{"cvss_score":9.8,"headline":"Insecure default value for CORS configuration","id":"CVE-2022-26969","kev_date_added":null,"published":"2022-12-26"},{"cvss_score":9.3,"headline":"Directus allows unauthenticated file upload and file modification due to lacking input sanitization","id":"CVE-2025-55746","kev_date_added":null,"published":"2025-08-20"},{"cvss_score":8.7,"headline":"Directus is Missing Cross-Origin Opener Policy","id":"CVE-2026-35408","kev_date_added":null,"published":"2026-04-06"},{"cvss_score":8.6,"headline":"Directus: Authorization-dependent response served from unsegmented cache key","id":"CVE-2026-61836","kev_date_added":null,"published":"2026-07-15"},{"cvss_score":8.6,"headline":"Directus's webhook trigger flows can leak sensitive data","id":"CVE-2025-30353","kev_date_added":null,"published":"2025-03-26"},{"cvss_score":8.5,"headline":"Directus has a Path Traversal and Broken Access Control in File Management API","id":"CVE-2026-39942","kev_date_added":null,"published":"2026-04-09"},{"cvss_score":8.2,"headline":"Directus MySQL accent insensitive email matching","id":"CVE-2024-27295","kev_date_added":null,"published":"2024-03-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["directus"]},"summary":"Attackers can enumerate existing SSO users by observing specific error messages when attempting local authentication with SSO-linked emails.","url":"https://insights.sbomify.com/CVE-2024-39896/"}