CVE-2025-11490
📋 TL;DR
This CVE describes an OS command injection vulnerability in DesktopCommanderMCP up to version 0.2.13. Attackers can execute arbitrary commands on the system by manipulating the extractBaseCommand function in the Absolute Path Handler component. Users of DesktopCommanderMCP versions 0.2.13 and earlier are affected.
💻 Affected Systems
- wonderwhy-er DesktopCommanderMCP
📦 What is this software?
Desktopcommandermcp by Wonderwhy Er
⚠️ Risk & Real-World Impact
Worst Case
Full system compromise allowing remote attackers to execute arbitrary commands with the privileges of the DesktopCommanderMCP process, potentially leading to data theft, ransomware deployment, or complete system takeover.
Likely Case
Limited command execution within the context of the application's permissions, potentially allowing file system access, data exfiltration, or lateral movement within the network.
If Mitigated
If proper input validation and sandboxing are implemented, impact is limited to the application's restricted execution environment with minimal system access.
🎯 Exploit Status
Exploit details have been publicly disclosed but no proof-of-concept code is available. Exploitation requires understanding of the command injection vector and access to trigger the vulnerable function.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Version after 0.2.13 (check GitHub for latest)
Vendor Advisory: https://github.com/wonderwhy-er/DesktopCommanderMCP/issues/218
Restart Required: No
Instructions:
1. Check current version with 'npm list desktopcommandermcp' or similar package manager command. 2. Update to latest version using package manager: 'npm update desktopcommandermcp' or equivalent. 3. Verify update completed successfully.
🔧 Temporary Workarounds
Input Validation Enhancement
allImplement strict input validation for command parameters to prevent path traversal and command injection attempts.
Implement validation in command-manager.ts to sanitize all user inputs before processing
Sandbox Execution
allRun DesktopCommanderMCP with minimal privileges and in a restricted execution environment.
Run as non-privileged user, use containerization, or implement process sandboxing
🧯 If You Can't Patch
- Network segmentation: Isolate systems running vulnerable versions from critical network segments
- Monitor for suspicious command execution patterns and implement strict logging of all command invocations
🔍 How to Verify
Check if Vulnerable:
Check package.json or run 'npm list desktopcommandermcp' to see if version is 0.2.13 or earlier
Check Version:
npm list desktopcommandermcp | grep desktopcommandermcp
Verify Fix Applied:
After update, verify version is greater than 0.2.13 using 'npm list desktopcommandermcp'
📡 Detection & Monitoring
Log Indicators:
- Unusual command execution patterns, unexpected absolute paths in command parameters, commands with shell metacharacters
Network Indicators:
- Unexpected outbound connections from DesktopCommanderMCP process, command and control traffic patterns
SIEM Query:
process.name:"DesktopCommanderMCP" AND (command_line:*".."* OR command_line:*"/"* OR command_line:*"|"* OR command_line:*"&"* OR command_line:*";"*)
🔗 References
- https://github.com/wonderwhy-er/DesktopCommanderMCP/issues/218
- https://github.com/wonderwhy-er/DesktopCommanderMCP/issues/218#issue-3343855120
- https://github.com/wonderwhy-er/DesktopCommanderMCP/issues/218#issuecomment-3214135034
- https://vuldb.com/?ctiid.327609
- https://vuldb.com/?id.327609
- https://vuldb.com/?submit.668005
- https://github.com/wonderwhy-er/DesktopCommanderMCP/issues/218
- https://github.com/wonderwhy-er/DesktopCommanderMCP/issues/218#issue-3343855120
- https://github.com/wonderwhy-er/DesktopCommanderMCP/issues/218#issuecomment-3214135034