CVE-2026-20959
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 input during web page generation ('cross-site scripting') in Microsoft Office SharePoint allows an authorized attacker to perform spoofing 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 confidenceThis is a stored cross-site scripting (XSS) vulnerability in Microsoft Office SharePoint where improper input neutralization allows an authenticated attacker to inject malicious scripts into web pages, enabling session hijacking and credential theft through spoofing.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 versionRun PowerShell command: Get-SPFarm | Select-Object BuildVersion, or check Central Administration > System Settings > Manage servers in this farm, or inspect the SharePoint DLL version in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\ISAPI\Microsoft.SharePoint.dllAffected if The version is SharePoint Server 2016, SharePoint Server 2019, or any build lower than 16.0.19127.20442
-
Verify SharePoint web application is accessibleConfirm the SharePoint web application is exposed via IIS and accessible to network users rather than localhost-onlyAffected if The SharePoint sites are publicly or internally accessible over the network, increasing exposure to authenticated attackers
-
Check authentication configurationReview SharePoint web application authentication providers in Central Administration > Manage web applications > Authentication Providers, noting whether forms-based or Windows authentication is enabledAffected if Any non-anonymous authentication method is configured, allowing authenticated users to submit content that could contain malicious scripts
-
Determine if external sharing is enabledCheck SharePoint external sharing settings via SharePoint Admin Center or PowerShell: Get-SPOExternalSharingConfiguration or Get-SPWebApplication | Get-SPExternalSecurityOptionsAffected if External sharing is enabled, allowing external users with accounts to inject malicious content
-
Identify user-facing input fieldsManually review SharePoint list forms, wiki pages, discussion boards, or any custom SharePoint solutions that accept and store user-supplied contentAffected if Any feature allowing authenticated users to create or modify content that gets rendered to other users is in use
The environment is affected if SharePoint Server 2016 or 2019 is installed, or if the build version is below 16.0.19127.20442, and the server accepts authenticated user content that could be stored and displayed to other users.
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
Implement proper input validation, output encoding, and Content Security Policy (CSP) headers in SharePoint; review and sanitize all user-supplied content before rendering.
SharePoint Server 2016/2019 to build 16.0.19127.20442 or later (latest supported cumulative update)
- 1. Review Microsoft SharePoint Server build 16.0.19127.20442 release notes on msrc.microsoft.com to understand the security update details
- 2. Identify the current SharePoint Server build version in your environment using SharePoint Administration Center or Get-SPFarm cmdlet
- 3. Schedule a maintenance window for the update process
- 4. Perform a full backup of SharePoint Server databases and farm configuration before applying updates
- 5. Apply the appropriate cumulative update or security hotfix that includes build 16.0.19127.20442 or later
- 6. Run the SharePoint Products Configuration Wizard (PSConfig) after applying the update
- 7. Verify the update was successful by confirming the new build version and testing SharePoint functionality
- 8. Validate that the XSS vulnerability is remediated by reviewing the Microsoft security bulletin
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-20959 — 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-20959 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