CVE-2026-20947
vulnerability analysis and mitigation

Overview

CVE-2026-20947 is a SQL injection vulnerability in Microsoft Office SharePoint that allows an authenticated attacker to execute arbitrary code over a network. It affects Microsoft SharePoint Server 2016 (Enterprise), SharePoint Server 2019, and SharePoint Server Subscription Edition (prior to version 16.0.19127.20442). The vulnerability was disclosed and patched on January 13, 2026, as part of Microsoft's January 2026 Patch Tuesday security updates. It carries a CVSS v3.1 base score of 8.8 (High) (Microsoft MSRC, Feedly).

Technical details

The vulnerability is classified as CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), meaning user-supplied input is not properly sanitized before being incorporated into SQL queries executed by SharePoint Server. An authenticated attacker with low privileges (e.g., Site Member permissions) can craft malicious SQL input delivered over the network — requiring no user interaction — to trigger code execution on the server. The attack vector is network-based with low complexity, making it accessible to any authenticated user without elevated privileges. No public proof-of-concept exploit code has been identified at this time (Microsoft MSRC, Feedly).

Impact

Successful exploitation results in remote code execution (RCE) with high impact across confidentiality, integrity, and availability — effectively granting an attacker complete control over the affected SharePoint Server instance. An attacker could access sensitive data stored in SharePoint, modify configurations and content, disrupt service availability, and potentially use the compromised server as a pivot point for lateral movement within the organization's network. Given SharePoint's typical role as a central collaboration and document management platform, exploitation could expose large volumes of sensitive organizational data (Feedly).

Exploitation steps

  1. Reconnaissance: Identify internet-facing Microsoft SharePoint Server instances (2016, 2019, or Subscription Edition prior to 16.0.19127.20442) using tools such as Shodan, Censys, or targeted network scanning.
  2. Obtain authentication: Acquire valid SharePoint credentials — even low-privilege Site Member access is sufficient. This could be achieved via phishing, credential stuffing, or purchasing credentials from underground markets.
  3. Identify injectable endpoint: Probe SharePoint application endpoints that process user-supplied input incorporated into SQL queries, looking for parameters vulnerable to SQL injection.
  4. Craft SQL injection payload: Construct a malicious SQL payload designed to escape the query context and execute operating system commands (e.g., via xp_cmdshell or equivalent SQL Server features), or to exfiltrate data.
  5. Submit payload: Send the crafted HTTP request containing the SQL injection payload to the vulnerable SharePoint endpoint over the network.
  6. Achieve code execution: The injected SQL command executes on the backend database server with SharePoint's service account privileges, enabling reverse shell establishment, data exfiltration, or further lateral movement within the environment (Microsoft MSRC, Feedly).

Indicators of compromise

  • Network: Unusual or malformed HTTP requests to SharePoint endpoints containing SQL metacharacters (e.g., ', --, UNION, SELECT, xp_cmdshell) in query parameters or POST body fields; unexpected outbound connections from the SharePoint server to external IPs.
  • Logs: SharePoint ULS logs or IIS access logs showing repeated requests with SQL-like patterns in parameters; SQL Server error logs indicating unexpected query failures or execution of stored procedures such as xp_cmdshell; authentication logs showing low-privilege accounts making unusual API calls.
  • File System: Unexpected new files (web shells, scripts) written to the SharePoint web root or temp directories; new scheduled tasks or services created under the SharePoint service account.
  • Process: Unusual child processes spawned by the SharePoint application pool worker process (e.g., cmd.exe, powershell.exe, net.exe, curl) or by SQL Server (sqlservr.exe spawning shell processes).

Mitigation and workarounds

Microsoft released security updates on January 13, 2026, addressing this vulnerability. Organizations should apply the following updates immediately:

  • SharePoint Server Subscription Edition: Update to version 16.0.19127.20442 or later
  • SharePoint Server 2019: Update to version 16.0.10417.20083 or later
  • SharePoint Server 2016 (Enterprise): Update to version 16.0.5535.1001 or later

As interim mitigations, organizations should restrict network access to SharePoint servers to trusted networks only, audit and minimize the number of authenticated users with access to SharePoint, and monitor for anomalous SQL-related activity in application and database logs. Updates are available through the Microsoft Security Update Guide (Microsoft MSRC).

Community reactions

The vulnerability was covered as part of broader January 2026 Patch Tuesday reporting, with security outlets including BleepingComputer, CyberScoop, GBHackers, and The Stack Technology noting it among the 114 flaws addressed that month (BleepingComputer, The Stack). The Zero Day Initiative (ZDI) included it in their January 2026 security update review (ZDI). Sophos and SANS ISC also published analyses of the January 2026 Patch Tuesday batch, highlighting SharePoint vulnerabilities as high-priority items for enterprise patching (Sophos, SANS ISC).

Additional resources


SourceThis report was generated using AI

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management