dbcve.org
Sharepoint ServerApplication · Microsoft

CVE-2026-45481

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

This is a Cross-Site Scripting (XSS) vulnerability in Microsoft Office SharePoint's web page generation functionality. An authenticated attacker can inject malicious scripts into SharePoint pages, allowing them to perform spoofing attacks by impersonating other users or entities within the SharePoint environment.

MitigationImplement proper input validation and output encoding for all user-supplied data rendered in SharePoint web pages. Apply Microsoft security updates for SharePoint when available.

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
    Run 'Get-SPfarm | Select BuildVersion' in SharePoint Management Shell or check Central Administration > System Settings > Manage servers in this farm
    Affected if Version is below 16.0.19725.20384, or the farm shows as SharePoint Server 2016 or 2019
  2. Confirm SharePoint Web Application is running
    In Central Administration > Application Management > Manage web applications, verify at least one web application exists and is started
    Affected if A web application is provisioned and accessible (SharePoint is serving pages to users)
  3. Check for authenticated user access
    In Central Administration > Application Management > Manage web applications, select a web application and click Authentication Providers to confirm classic or claims-based authentication is enabled for users
    Affected if Authentication providers are configured allowing authenticated users to access content
  4. Identify custom or third-party web parts that render user input
    Review installed solutions via 'Get-SPSolution' in SharePoint Management Shell and inspect any web parts that accept and display user-provided content in site pages
    Affected if Custom web parts, InfoPath forms, or list views that render user-supplied data are deployed

The environment is affected if the SharePoint Server version is 2016 or 2019 (or any version below 16.0.19725.20384) and web applications with authenticated user access are operational, allowing potential XSS injection in pages rendering user input.

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 rendered in SharePoint web pages. Apply Microsoft security updates for SharePoint when available.

Recommended fix Moderate confidence

SharePoint Server version >= 16.0.19725.20384 (or latest supported version for SharePoint 2016/2019)

  1. 1. Review Microsoft SharePoint Server compatibility and system requirements for version 16.0.19725.20384 or later
  2. 2. Perform a full backup of the SharePoint farm configuration and content databases
  3. 3. Test the upgrade in a non-production environment before deploying to production
  4. 4. Apply the latest Microsoft SharePoint Server updates to reach version 16.0.19725.20384 or newer
  5. 5. Verify the XSS vulnerability is remediated by testing the identified attack vector
  6. 6. Confirm all SharePoint services and web applications are functioning correctly post-upgrade
Caveat Major SharePoint upgrades may require Farm infrastructure changes, customizations compatibility review, and potential downtime; test thoroughly in staging first

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-45481 — 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-45481 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