dbcve.org
DesktopcommandermcpApplication · Wonderwhy Er

CVE-2025-11490

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-08
Fix available
A fix is available. Upgrade to after 0.2.13 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been found in wonderwhy-er DesktopCommanderMCP up to 0.2.13. The affected element is the function extractBaseCommand of the file src/command-manager.ts of the component Absolute Path Handler. Such manipulation leads to os command injection. The attack may be performed from remote. The exploit has been disclosed to the public and may be used. The vendor explains: "The usual use case is that AI is asked to do something, picks commands itself, and typically uses simple command names without absolute paths. It's curious why a user would ask the model to bypass restrictions this way. (...) This could potentially be a problem, but we are yet to hear reports of this being an issue in actual workflows. We'll leave this issue open for situations where people may report this as a problem for the long term."

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OS command injection vulnerability in DesktopCommanderMCP's extractBaseCommand function within src/command-manager.ts. The Absolute Path Handler component fails to properly sanitize input when processing absolute paths, allowing an attacker to inject arbitrary OS commands.

MitigationImplement strict input validation and sanitization for the path handling in extractBaseCommand to prevent command injection. Consider using allowlist validation or parameterized approaches for any command execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DesktopcommandermcpApplication
Affected:<= 0.2.13

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm DesktopCommanderMCP is installed
    Check for the DesktopCommanderMCP package in your node_modules or project dependencies. Look for it in package.json or run npm list desktopcommandermcp
    Affected if The package is present in your environment
  2. Identify the installed version
    Run npm list desktopcommandermcp or check your package-lock.json for the version number. Compare it to the affected range: <= 0.2.13
    Affected if The installed version is 0.2.13 or any lower version
  3. Locate the vulnerable source file
    Search for src/command-manager.ts in your DesktopCommanderMCP installation directory and verify the extractBaseCommand function exists
    Affected if The file and function are present in your installation
  4. Verify absolute path handling is in use
    Review your configuration or usage patterns to determine if absolute paths are being processed through the extractBaseCommand function
    Affected if Your workflows involve passing absolute file paths to the application
  5. Inspect input handling in extractBaseCommand
    Examine the extractBaseCommand function code in src/command-manager.ts for lack of input sanitization on path parameters, specifically looking for direct use of path data in command execution
    Affected if The function processes path input without proper validation or sanitization

You are affected if DesktopCommanderMCP version 0.2.13 or lower is installed and absolute paths are processed through the extractBaseCommand function in command-manager.ts

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 0.2.13
Interim mitigation

Implement strict input validation and sanitization for the path handling in extractBaseCommand to prevent command injection. Consider using allowlist validation or parameterized approaches for any command execution.

Recommended fix Moderate confidence

Check wonderwhy-er/DesktopCommanderMCP GitHub for releases newer than 0.2.13 (version 0.2.14 or later if available)

  1. 1. Identify the current installed version of DesktopCommanderMCP by checking package.json or running npm list desktopcommandermcp
  2. 2. Check the official GitHub repository (wonderwhy-er/DesktopCommanderMCP) for any releases newer than version 0.2.13 that address CVE-2025-11490
  3. 3. If a fixed version is available, upgrade by running: npm install desktopcommandermcp@latest or npm install desktopcommandermcp@<fixed_version>
  4. 4. Verify the upgrade was successful and the new version is installed
  5. 5. Test the application to ensure the command injection vulnerability is resolved and the Absolute Path Handler functions correctly
  6. 6. If no fixed version is available, consider implementing input validation/sanitization in the extractBaseCommand function in src/command-manager.ts to prevent command injection by validating that path inputs do not contain shell metacharacters
Caveat Check release notes for any breaking changes between current version and the target upgrade version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Desktopcommandermcp Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11490 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11490 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data