dbcve.org
Sharepoint ServerApplication · Microsoft

CVE-2026-47294

HIGH · 8.0 CVSS v3.1 Published 2026-06-01
Fix available
A fix is available. Upgrade to 16.0.19725.20280 or later.
See remediation →
84/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 an os command ('os command injection') in Microsoft Office SharePoint 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 an OS command injection vulnerability in Microsoft Office SharePoint that allows an authenticated attacker to execute arbitrary operating system commands on the server. The vulnerability stems from improper neutralization of special elements in user-supplied input that gets passed to system shell commands, enabling remote code execution with the privileges of the SharePoint application service account.

MitigationApply vendor patches when available; implement strict input validation and parameterized queries to prevent command injection; follow least-privilege principles for SharePoint service accounts; consider network segmentation to limit exposure.

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
Sharepoint ServerApplication
Affected:< 16.0.19725.20280= 2016= 2019

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

CVSS:3.1/AV:N/AC:L/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 SharePoint Server version via PowerShell
    Open SharePoint Management Shell and run: Get-SPProduct -LocalServer | Select-Object -Property Id, Name, Version, Build
    Affected if Version is lower than 16.0.19725.20280, or the build matches SharePoint 2016 or 2019 release builds (e.g., 16.0.xxxx.xxxx)
  2. Retrieve detailed build information
    Run: Get-SPFarm | Select-Object -Property BuildVersion, Version, DisplayVersion
    Affected if BuildVersion shows a number less than 16.0.19725.20280, or DisplayVersion shows 2016 or 2019
  3. Verify exact product version in Windows Registry
    Check registry key: HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\16.0\SharePoint\ProductVersion
    Affected if The Version value is lower than 16.0.19725.20280, or Version reflects SharePoint 2016/2019
  4. List installed SharePoint updates
    Open Control Panel > Programs > Programs and Features > View installed updates, or run: Get-HotFix | Where-Object {$_.Description -like '*SharePoint*'}
    Affected if No hotfix with KB number corresponding to the CVE patch is installed, or no patches have been applied after the CVE publication date
  5. Confirm SharePoint Server edition is in scope
    Verify the installed product is Microsoft SharePoint Server (not SharePoint Foundation/Online) by checking Central Administration > System Settings > Manage servers in this farm
    Affected if The farm shows SharePoint Server 2016 or 2019, or the edition displays as 'SharePoint Server' rather than Foundation

A system is affected if it runs any Microsoft SharePoint Server version below 16.0.19725.20280, including specifically SharePoint Server 2016 or 2019, and the security patch for this CVE has not been applied.

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 16.0.19725.20280 or later
Fixed in 16.0.19725.20280
Interim mitigation

Apply vendor patches when available; implement strict input validation and parameterized queries to prevent command injection; follow least-privilege principles for SharePoint service accounts; consider network segmentation to limit exposure.

Recommended fix Moderate confidence

SharePoint Server 2016/2019 with security update to version >= 16.0.19725.20280

  1. Identify the current SharePoint Server version by checking Central Administration > System Settings > Manage servers in this farm
  2. Navigate to the Microsoft Update Catalog or Microsoft Download Center to obtain the security update for this vulnerability
  3. Apply the appropriate security update (KB number specific to this CVE) to all SharePoint servers in the farm
  4. Run the SharePoint Products Configuration Wizard on each server after applying the update
  5. Verify the version has been updated to 16.0.19725.20280 or higher by checking the farm version in Central Administration
  6. Test critical SharePoint workflows and web parts to ensure functionality is intact
Caveat Standard SharePoint update - test in non-production first; may require downtime for update deployment

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

Fix this in Sharepoint Server Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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