CVE-2025-11490

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. Its 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. Well leave this issue open for situations where people may report this as a problem for the long term.

Weakness

The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.

Extended Description

Many protocols and products have their own custom command language. While OS or shell command strings are frequently discovered and targeted, developers may not realize that these other command languages might also be vulnerable to attacks.

Potential Mitigations

• Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
• When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
• Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/136.html
• https://cwe.mitre.org/data/definitions/15.html
• https://cwe.mitre.org/data/definitions/183.html
• https://cwe.mitre.org/data/definitions/248.html
• https://cwe.mitre.org/data/definitions/40.html
• https://cwe.mitre.org/data/definitions/43.html
• https://cwe.mitre.org/data/definitions/75.html
• https://cwe.mitre.org/data/definitions/76.html

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