dbcve.org
Sharepoint ServerApplication · Microsoft

CVE-2026-45464

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

This is a cross-site scripting (XSS) vulnerability in Microsoft Office SharePoint where improper input neutralization allows an attacker to inject malicious scripts into web pages. The vulnerability enables an unauthorized attacker to perform spoofing attacks over a network, likely by tricking users into executing malicious JavaScript in the context of a trusted SharePoint site.

MitigationApply the Microsoft security update for SharePoint when available, or implement input validation and output encoding controls. Review and sanitize user-supplied content within SharePoint pages and web parts.

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. Check SharePoint Server version via Central Administration
    Open SharePoint Central Administration > System Settings > Manage servers in this farm. Locate the Build number column for each server.
    Affected if The Build number is lower than 16.0.19725.20384, or the version shows SharePoint Server 2016 or 2019.
  2. Check SharePoint version via PowerShell
    Open SharePoint Management Shell and run: Get-SPFarm | Select-Object BuildVersion
    Affected if The returned BuildVersion is below 16.0.19725.20384, or displays as version 2016 or 2019.
  3. Identify the SharePoint edition
    In Central Administration, go to Upgrade and Migration > Check product and patch installation status, or run: (Get-SPFarm).BuildVersion
    Affected if The farm runs SharePoint Server 2016 or 2019 (any build), or any version with build number less than 16.0.19725.20384.
  4. Verify if the farm is receiving Microsoft updates
    In Central Administration > System Settings > Manage servers in this farm, check the Configuration Database version and compare to Microsoft Security Response Center bulletins for SharePoint.
    Affected if The farm has not received the security patch for CVE-2026-45464, indicated by a version still within the affected range.

A SharePoint Server farm is affected if it runs version 2016 or 2019, or any build prior to 16.0.19725.20384, and has not yet received the corresponding security patch.

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 the Microsoft security update for SharePoint when available, or implement input validation and output encoding controls. Review and sanitize user-supplied content within SharePoint pages and web parts.

Recommended fix Low confidence

SharePoint Server 2016/2019 to build 16.0.19725.20384 or later

  1. 1. Back up the SharePoint farm configuration and content databases before applying any updates.
  2. 2. Verify the current SharePoint build version by navigating to SharePoint Central Administration > Upgrade and Migration > Check product and farm installation status.
  3. 3. Download the latest SharePoint Server updates from Microsoft Update Catalog or the Microsoft Download Center matching build 16.0.19725.20384 or later.
  4. 4. Run the SharePoint Server update installer on all servers in the farm, following the standard patch installation sequence (install on application servers first, then front-end servers).
  5. 5. After installation, run the SharePoint Products Configuration Wizard (PSConfig) on each server in the farm.
  6. 6. Verify successful patching by checking the build number again in Central Administration.
  7. 7. Test critical SharePoint workflows and web parts to ensure functionality is intact.
  8. 8. Monitor the SharePoint ULS logs for any errors related to the patch or XSS-related vulnerabilities.
Caveat Standard SharePoint cumulative update risks apply - test in non-production environment first; some farm solutions may require retesting after security 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-45464 — 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-45464 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