{"answers":{"affected":"2 open source packages ship an affected version, including directus. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-53889 in the wild and no public exploit code.","fix":"Upgrade directus to 11.9.0 or later.","what":"CVE-2025-53889 is a medium-severity missing authorization vulnerability in Monospace Directus, published on 14 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-53889 and fix it if it is affected.\n\nWhat it is: CVE-2025-53889 is a medium-severity missing authorization vulnerability in Monospace Directus, published on 14 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-53889 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- directus (npm): affected all versions; fixed in 11.9.0\n- directus (npm): affected all versions; fixed in 11.9.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-53889/ (Markdown: https://insights.sbomify.com/CVE-2025-53889/index.md)","id":"CVE-2025-53889","markdown":"https://insights.sbomify.com/CVE-2025-53889/index.md","name":"CVE-2025-53889","record":{"aliases":["GHSA-7cvf-pxgp-42fc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Directus headless CMS","requires_auth":"none","summary":"Attackers can execute manual trigger Flows without authentication or proper permissions, potentially accessing data or performing actions on their behalf.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"directus","vendor":"monospace"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Directus is a real-time API and App dashboard for managing SQL database content. Starting in version 9.12.0 and prior to version 11.9.0, Directus Flows with a manual trigger are not validating whether the user triggering the Flow has permissions to the items provided as payload to the Flow. Depending on what the Flow is set up to do this can lead to the Flow executing potential tasks on the attacker's behalf without authenticating. Bad actors could execute the manual trigger Flows without authentication, or access rights to the said collection(s) or item(s). Users with manual trigger Flows configured are impacted as these endpoints do not currently validate if the user has read access to `directus_flows` or to the relevant collection/items. The manual trigger Flows should have tighter security requirements as compared to webhook Flows where users are expected to perform do their own checks. Version 11.9.0 fixes the issue. As a workaround, implement permission checks for read access to Flows and read access to relevant collection/items.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Directus missing permission checks for manual trigger Flows","id":"CVE-2025-53889","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":3,"next":{"headline":"pyLoad vulnerable to remote code execution through js2py onCaptchaResult","id":"CVE-2025-53890"},"packages":[{"ecosystem":"npm","fixed":["11.9.0"],"introduced":["0"],"last_affected":[],"package":"directus","purl":null,"source":"GHSA-7cvf-pxgp-42fc"},{"ecosystem":"npm","fixed":["11.9.0"],"introduced":["0"],"last_affected":[],"package":"directus","purl":"pkg:npm/directus","source":"GHSA-7cvf-pxgp-42fc"}],"prev":{"headline":"Memory corruption in RIOT","id":"CVE-2025-53888"},"products":["directus"],"published":"2025-07-14","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-15","vendors":["directus"]},"summary":"Attackers can execute manual trigger Flows without authentication or proper permissions, potentially accessing data or performing actions on their behalf.","url":"https://insights.sbomify.com/CVE-2025-53889/"}