CVE-2026-20947
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 · uneditedImproper neutralization of special elements used in an sql command ('sql 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 confidenceSQL injection vulnerability in Microsoft Office SharePoint enabling an authenticated attacker to execute arbitrary code through specially crafted SQL commands. The improper neutralization of special elements in SQL queries allows remote code execution over the network.
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< 16.0.19127.20442= 2016= 2019CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SharePoint Server versionUse SharePoint Central Administration (System Settings > Manage servers in this farm) or run Get-SPFarm | Select-Object BuildVersion in SharePoint Management Shell to retrieve the installed version numberAffected if The version is below 16.0.19127.20442 or matches SharePoint Server 2016 or 2019
-
Confirm SharePoint editionVerify the farm is running Microsoft SharePoint Server (not SharePoint Foundation) by checking farm products in Central AdministrationAffected if The edition is SharePoint Server 2016 or 2019 (these specific versions are listed as affected)
-
Compare version against thresholdDocument the full build version (for example, 16.0.14727.20442) and compare numerically to the fixed version 16.0.19127.20442Affected if The installed build version is less than 16.0.19127.20442 (any version below this threshold is vulnerable)
You are affected if your SharePoint Server installation is version 2016, 2019, or any build version lower than 16.0.19127.20442.
Generated from the published advisory. Verify against your own configuration.
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 · scoped16.0.19127.20442
Apply Microsoft security patches for SharePoint addressing the SQL injection vulnerability and implement parameterized queries or stored procedures for database interactions.
Microsoft Security Update for CVE-2026-20947 (build 16.0.19127.20442 or later)
- Check current SharePoint Server version by reviewing installed updates or farm version in SharePoint Central Administration
- Navigate to Microsoft Security Response Center (msrc.microsoft.com) and search for CVE-2026-20947
- Download the applicable security update for your SharePoint Server version (2016 or 2019)
- Apply the security update following Microsoft installation instructions (typically via running the update on all servers in the SharePoint farm)
- Run SharePoint Products Configuration Wizard (PSConfig) on all servers in the farm after patching
- Verify the patch was applied successfully by checking the build version matches 16.0.19127.20442 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-20947 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-20947 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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