{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11489 exists.","fix":"No fix has been published for CVE-2025-11489 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-11489 is a low-severity path traversal vulnerability in wonderwhy-er DesktopCommanderMCP, published on 8 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-11489 and fix it if it is affected.\n\nWhat it is: CVE-2025-11489 is a low-severity path traversal vulnerability in wonderwhy-er DesktopCommanderMCP, published on 8 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11489 exists.\n\nAffected product: wonderwhy-er DesktopCommanderMCP. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-11489/ (Markdown: https://insights.sbomify.com/CVE-2025-11489/index.md)","id":"CVE-2025-11489","markdown":"https://insights.sbomify.com/CVE-2025-11489/index.md","name":"CVE-2025-11489","record":{"aliases":["GHSA-2jf9-5hf7-r448"],"analysis":{"component_type":"developer_tool","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Desktop Commander MCP","requires_auth":"low_privilege","summary":"Local attackers can bypass path restrictions via symlink following in Desktop Commander MCP, potentially accessing or modifying unauthorized files.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"desktopcommandermcp","vendor":"wonderwhy-er"}],"cvss":{"score":2,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-61","name":"UNIX Symbolic Link (Symlink) Following"},{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"A security vulnerability has been detected in wonderwhy-er DesktopCommanderMCP up to 0.2.13. This vulnerability affects the function isPathAllowed of the file src/tools/filesystem.ts. The manipulation leads to symlink following. The attack can only be performed from a local environment. The attack's complexity is rated as high. It is stated that the exploitability is difficult. The exploit has been disclosed publicly and may be used. The vendor explains: \"Our restriction features are designed as guardrails for LLMs to help them stay closer to what users want, rather than hardened security boundaries. (...) For users where security is a top priority, we continue to recommend using Desktop Commander with Docker, which provides actual isolation. (...) We'll keep this issue open for future consideration if we receive more user demand for improved restrictions.\" This vulnerability only affects products that are no longer supported by the maintainer.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"wonderwhy-er DesktopCommanderMCP filesystem.ts isPathAllowed symlink","id":"CVE-2025-11489","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":0,"n_references":6,"next":{"headline":"wonderwhy-er DesktopCommanderMCP Absolute Path command-manager.ts extractBaseCommand os command injection","id":"CVE-2025-11490"},"packages":[],"prev":{"headline":"D-Link DIR-852 HNAP1 command injection","id":"CVE-2025-11488"},"products":["DesktopCommanderMCP"],"published":"2025-10-08","related":[{"cvss_score":5.3,"headline":"wonderwhy-er DesktopCommanderMCP Absolute Path command-manager.ts extractBaseCommand os command injection","id":"CVE-2025-11490","kev_date_added":null,"published":"2025-10-08"},{"cvss_score":5.3,"headline":"wonderwhy-er DesktopCommanderMCP command-manager.ts CommandManager os command injection","id":"CVE-2025-11491","kev_date_added":null,"published":"2025-10-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-10-23","vendors":["wonderwhy-er"]},"summary":"Local attackers can bypass path restrictions via symlink following in Desktop Commander MCP, potentially accessing or modifying unauthorized files.","url":"https://insights.sbomify.com/CVE-2025-11489/"}