dbcve.org
Visual Studio 2022Application · Microsoft

CVE-2025-47959

HIGH · 7.1 CVSS v3.1 Published 2025-06-13
Fix available
A fix is available. Upgrade to 17.8.22 / 17.10.16 or later.
See remediation →
75/100
Remediation priority · High
Remotely reachable

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
Improper neutralization of special elements used in a command ('command injection') in Visual Studio allows an authorized attacker to execute code over a network.

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 · moderate confidence

This is a command injection vulnerability in Visual Studio where special elements used in system commands are not properly neutralized. An authorized attacker can exploit this to execute arbitrary code over a network by injecting malicious commands through unsanitized input that gets passed to system calls.

MitigationApply the vendor-supplied security patch for Visual Studio when available. In the interim, restrict network access to trusted users only and validate/sanitize any user-supplied input before passing it to system commands.

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
Visual Studio 2022Application
Affected:>= 17.8.0, < 17.8.22>= 17.10.0, < 17.10.16>= 17.12.0, < 17.12.9>= 17.14.0, < 17.14.5

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
High
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/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. Check Visual Studio 2022 installed version
    Open Visual Studio and go to Help > About Microsoft Visual Studio to view the version number, or check Programs and Features in Control Panel for the installed version
    Affected if The installed version is 17.8.0 through 17.8.21, 17.10.0 through 17.10.15, 17.12.0 through 17.12.8, or 17.14.0 through 17.14.4 (any version in the affected ranges)
  2. Identify if Visual Studio invokes system commands with external input
    Review any custom build tasks, extensions, or external tools integrated with Visual Studio that pass user-supplied or network-received data to system command execution functions (such as system(), exec(), or ShellExecute APIs)
    Affected if Your Visual Studio workflow includes features or extensions that accept external input and pass it to system calls without sanitization

You are affected if Visual Studio 2022 is at an affected version AND external or user-supplied input can reach system command execution within your Visual Studio environment.

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 17.8.22 / 17.10.16 / 17.12.9 or later
Fixed in 17.8.2217.10.1617.12.9
Interim mitigation

Apply the vendor-supplied security patch for Visual Studio when available. In the interim, restrict network access to trusted users only and validate/sanitize any user-supplied input before passing it to system commands.

Recommended fix High confidence

Visual Studio 2022 version 17.14.5 (or the minimum fixed version for your release line: 17.8.22, 17.10.16, 17.12.9, or 17.14.5)

  1. Open Visual Studio Installer on your machine
  2. Click on the Visual Studio 2022 instance you need to update
  3. Click the 'Update' button to check for updates
  4. Alternatively, download Visual Studio 2022 version 17.14.5 (or the appropriate fixed version for your release line) from the official Microsoft Visual Studio downloads page: https://visualstudio.microsoft.com/downloads/
  5. Run the installer and follow the prompts to complete the update
  6. Restart Visual Studio after the update completes
  7. Verify the installed version by going to Help > About Microsoft Visual Studio and confirming the version number matches the expected fixed release
Caveat Standard upgrade risks apply - verify your extensions and workloads are compatible with the new version before production use

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

Fix this in Visual Studio 2022 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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