{"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-2025-64746 exists.","fix":"Upgrade directus to 11.13.0 or later.","what":"CVE-2025-64746 is a medium-severity missing authorization vulnerability in Monospace Directus, published on 13 Nov 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-64746 and fix it if it is affected.\n\nWhat it is: CVE-2025-64746 is a medium-severity missing authorization vulnerability in Monospace Directus, published on 13 Nov 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64746 exists.\n\nAffected packages and fixed versions:\n- directus (npm): affected all versions; fixed in 11.13.0\n- directus (npm): affected all versions; fixed in 11.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-2025-64746/ (Markdown: https://insights.sbomify.com/CVE-2025-64746/index.md)","id":"CVE-2025-64746","markdown":"https://insights.sbomify.com/CVE-2025-64746/index.md","name":"CVE-2025-64746","record":{"aliases":["GHSA-9x5g-62gj-wqf2"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Directus CMS","requires_auth":"low_privilege","summary":"Attackers or unauthorized users may access or modify data due to stale permissions when deleted field names are reused in Directus.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"directus","vendor":"monospace"}],"cvss":{"score":4.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"Directus is a real-time API and App dashboard for managing SQL database content. Prior to version 11.13.0, Directus does not properly clean up field-level permissions when a field is deleted. When a field is removed from a collection, its reference in the permissions table remains intact. This stale reference creates a security gap: if another field is later created using the same name, it inherits the outdated permission entry. This behavior can unintentionally grant roles access to data they should not be able to read or modify. The issue is particularly risky in multi-tenant or production environments, where administrators may reuse field names, assuming old permissions have been fully cleared. Version 11.13.0 fixes the issue.","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 has Improper Permission Handling on Deleted Fields","id":"CVE-2025-64746","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"monospace:directus","products":["monospace:directus"],"type":"missing_authorization","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"Directus Vulnerable to Stored Cross-site Scripting","id":"CVE-2025-64747"},"packages":[{"ecosystem":"npm","fixed":["11.13.0"],"introduced":["0"],"last_affected":[],"package":"directus","purl":null,"source":"GHSA-9x5g-62gj-wqf2"},{"ecosystem":"npm","fixed":["11.13.0"],"introduced":["0"],"last_affected":[],"package":"directus","purl":"pkg:npm/directus","source":"GHSA-9x5g-62gj-wqf2"}],"prev":{"headline":"Astro development server error page vulnerable to reflected Cross-site Scripting","id":"CVE-2025-64745"},"products":["directus"],"published":"2025-11-13","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-13","vendors":["directus"]},"summary":"Attackers or unauthorized users may access or modify data due to stale permissions when deleted field names are reused in Directus.","url":"https://insights.sbomify.com/CVE-2025-64746/"}