dbcve.org
Sharepoint ServerApplication · Microsoft

CVE-2026-33113

MEDIUM · 6.1 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 16.0.19725.20384 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 input during web page generation ('cross-site scripting') in Microsoft Office SharePoint allows an unauthorized 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 confidence

Cross-site scripting (XSS) vulnerability in Microsoft Office SharePoint allows unauthenticated attackers to inject malicious scripts into web pages generated by SharePoint. The improper neutralization of input enables attackers to perform spoofing attacks by tricking users into executing attacker-controlled code within the context of a trusted SharePoint site.

MitigationApply Microsoft security patches for SharePoint when available; validate and encode all user inputs before rendering in web pages; implement Content Security Policy (CSP) headers to mitigate XSS execution.

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.20384= 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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed SharePoint Server version
    Run PowerShell command: Get-SPFarm | Select-Object BuildVersion. Or via Central Administration > System Settings > Manage servers in farm
    Affected if Version shows 2016 or 2019, OR build number is below 16.0.19725.20384
  2. Confirm SharePoint edition is Server
    Run PowerShell: (Get-SPFarm).Products. This returns GUIDs indicating installed products. SharePoint Server 2016/2019 will show product IDs for respective versions.
    Affected if Returns SharePoint Server 2016 or 2019 GUID
  3. Identify web-facing sites accepting user input
    Review web applications via Central Administration > Web Applications > Manage Web Applications. Identify sites with custom lists, forms, or web parts that accept user-submitted content.
    Affected if Any web-accessible site exists with user input forms, discussion boards, or custom web parts
  4. Check for custom or third-party web parts
    Review deployed web parts via SharePoint Designer or: Get-SPWebPartPackage -WebApplication [url]. Focus on web parts that render user-supplied data.
    Affected if Custom or third-party web parts are deployed that handle user input

Your SharePoint Server 2016 or 2019 installation is affected if the build version is below 16.0.19725.20384 and web-facing sites accept any user-supplied content.

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.20384 or later
Fixed in 16.0.19725.20384
Interim mitigation

Apply Microsoft security patches for SharePoint when available; validate and encode all user inputs before rendering in web pages; implement Content Security Policy (CSP) headers to mitigate XSS execution.

Recommended fix High confidence

SharePoint Server build 16.0.19725.20384 or later

  1. 1. Identify the current SharePoint Server version by navigating to SharePoint Central Administration > System Settings > Manage farm servers or running Get-SPFarm | Select-Object BuildVersion
  2. 2. Backup the SharePoint farm configuration and content databases before applying any updates
  3. 3. Download the security update for Microsoft SharePoint Server from the Microsoft Security Response Center (msrc.microsoft.com) corresponding to CVE-2026-33113
  4. 4. Install the update on all SharePoint servers in the farm, starting with the application servers
  5. 5. Run the SharePoint Products Configuration Wizard (psconfig) on each server to complete the upgrade
  6. 6. Verify the build version has been updated to 16.0.19725.20384 or higher
Caveat Standard SharePoint update risks apply - ensure testing in non-production environment first; some custom solutions may require recompilation or updates after cumulative updates

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

Fix this in Sharepoint Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

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