dbcve.org
Sharepoint ServerApplication · Microsoft

CVE-2026-47637

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 16.0.19725.20384 or later.
See remediation →
58/100
Remediation priority · Elevated
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 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 confidence

Cross-site scripting (XSS) vulnerability in Microsoft Office SharePoint allows an authenticated attacker to inject malicious scripts into web pages, enabling session hijacking and content spoofing. The vulnerability stems from improper input neutralization during page generation.

MitigationImplement proper input validation and output encoding for all user-supplied data in SharePoint. Apply Microsoft SharePoint security patches when available and validate authorization controls on affected endpoints.

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
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 checks

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

  1. Identify SharePoint Server version
    Open SharePoint Management Shell and run: (Get-SPFarm).BuildVersion.ToString() or check Central Administration > System Settings > Manage farm configuration
    Affected if Version is 2016, 2019, or below 16.0.19725.20384
  2. Confirm SharePoint edition is Server
    Verify the installation is SharePoint Server (not SharePoint Online) by checking installed programs or running: Get-PSSnapin | Where-Object {$_.Name -like '*SharePoint*'}
    Affected if Product is Microsoft SharePoint Server and version is vulnerable
  3. Check for authenticated access points
    Review web applications in Central Administration > Application Management > Manage web applications. Confirm Windows or Forms authentication is enabled for any web apps
    Affected if Web applications accept authenticated user connections (default configuration)
  4. Audit custom web parts and controls
    Review web.config files and _layouts folder for custom web parts or Farm Solutions that handle user input without proper encoding. Use SharePoint Designer or PowerShell: Get-SPWebPart
    Affected if Custom or third-party web parts process user-supplied data without output encoding

Environment is affected if running SharePoint Server 2016 or 2019, or any version prior to 16.0.19725.20384, with authenticated web applications exposed to users.

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

Implement proper input validation and output encoding for all user-supplied data in SharePoint. Apply Microsoft SharePoint security patches when available and validate authorization controls on affected endpoints.

Recommended fix Moderate confidence

SharePoint Server 2016 or 2019 with version 16.0.19725.20384 or higher

  1. 1. Verify current SharePoint Server version by navigating to SharePoint Central Administration > System Settings > Manage servers in this farm
  2. 2. Create a full backup of all SharePoint databases and the farm configuration before proceeding with any update
  3. 3. Test the update in a non-production environment first to verify compatibility with your custom solutions and workflows
  4. 4. Download the appropriate SharePoint Server update from Microsoft Update Catalog or Volume Licensing service center matching version 16.0.19725.20384 or later
  5. 5. Run the SharePoint Server update installer on each server in the farm, following the Microsoft update installation sequence (typically: application servers first, then web front ends)
  6. 6. After installation, run the SharePoint Products Configuration Wizard (PSConfig) on each server to complete the upgrade process
  7. 7. Verify the version has been updated by checking the farm version in Central Administration matches or exceeds 16.0.19725.20384
  8. 8. Test critical SharePoint functionality including authentication, workflows, and custom solutions to ensure proper operation
Caveat Major SharePoint updates may require farm rebuild in certain scenarios; custom solutions and third-party add-ins should be tested for compatibility before production deployment

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
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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