dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-11202

CRITICAL · 9.8 CVSS v3.0 Published 2025-10-29
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
win-cli-mcp-server resolveCommandPath Command Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of win-cli-mcp-server. Authentication is not required to exploit this vulnerability. The specific flaw exists within the implementation of the resolveCommandPath method. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-27787.

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

A command injection vulnerability exists in the resolveCommandPath method of win-cli-mcp-server. The flaw allows unauthenticated remote attackers to inject malicious commands through unsanitized user input that gets directly passed to a system call, enabling arbitrary code execution in the context of the service account.

MitigationImplement strict input validation and sanitization on the resolveCommandPath method, using parameterized APIs or allowlists instead of passing user input directly to system calls. Consider using safe API alternatives that avoid shell execution.

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

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.0/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. Identify if win-cli-mcp-server is installed
    Run 'npm list win-cli-mcp-server' or check the application's package.json dependencies, or look for the process running win-cli-mcp-server
    Affected if The package is present in node_modules, package.json, or running as a process
  2. Determine the installed version
    Run 'npm list win-cli-mcp-server --depth=0' to see the exact version number, or inspect package-lock.json for the installed version
    Affected if The installed version is unknown or within any affected range (no specific safe version provided in CVE data)
  3. Verify the resolveCommandPath method is exposed to user input
    Review application logs, API endpoints, or network configuration to determine if external users can supply input to the resolveCommandPath method
    Affected if The method accepts network requests or external input without authentication
  4. Inspect input validation in resolveCommandPath
    Examine the source code of win-cli-mcp-server for the resolveCommandPath function and check if user-supplied strings are validated before being used in system calls
    Affected if User input is passed directly to system calls without sanitization or allowlist validation

You are affected if win-cli-mcp-server is installed and the resolveCommandPath method can receive unauthenticated user input that is not validated before being used in system calls.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Implement strict input validation and sanitization on the resolveCommandPath method, using parameterized APIs or allowlists instead of passing user input directly to system calls. Consider using safe API alternatives that avoid shell execution.

Recommended fix High confidence
  1. Review the fix commit at https://github.com/simon-ami/win-cli-mcp-server/commit/521b4a34190d03bde7d433d213c36357181a6d09 to understand the code changes
  2. Identify the resolveCommandPath method in the codebase
  3. Apply the changes from the fix commit, which should add proper validation of user-supplied strings before using them in system calls
  4. Rebuild and redeploy the win-cli-mcp-server service
  5. Verify the fix does not introduce regressions by testing command resolution functionality

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11202 — 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-11202 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