CVE-2026-45465
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 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 confidenceThis is a cross-site scripting (XSS) vulnerability in Microsoft Office SharePoint where improper neutralization of input during web page generation allows attackers to inject malicious scripts into web pages, potentially enabling spoofing attacks against users.
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.19725.20384= 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 installed SharePoint Server versionRun PowerShell command: (Get-SPFarm).BuildVersion or check Central Administration > System Settings > Manage farm configuration. The version format is typically 16.0.x.x for SharePoint 2016/2019 and 16.0.19725.x.x for newer versions.Affected if The version is 2016 (16.0.x.x), 2019 (16.0.x.x), or any version earlier than 16.0.19725.20384
-
Confirm SharePoint edition and buildIn PowerShell, run: Get-SPServerFarm or check the SharePoint Central Administration site version information page.Affected if The farm shows SharePoint Server 2016, SharePoint Server 2019, or a build number lower than 16.0.19725.20384
-
Determine if web content rendering is in useReview SharePoint web applications and site collections that render user-supplied content in pages. Check if custom web parts, page templates, or third-party solutions that display user input are deployed.Affected if Any web applications exist that accept and display user input through SharePoint pages, web parts, or customizations that could be exploited for XSS injection.
You are affected if your SharePoint Server version is 2016, 2019, or any build earlier than 16.0.19725.20384, and your environment renders user-supplied content in SharePoint pages.
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.19725.20384
Apply available Microsoft security patches for SharePoint and implement proper input validation and output encoding for user-supplied content.
Microsoft security update to version 16.0.19725.20384 or later for SharePoint Server 2016/2019
- Check current SharePoint Server version via Central Administration > System Settings > Manage servers in this farm
- Identify which SharePoint Server version (2016 or 2019) is running
- Navigate to the Microsoft Security Response Center (msrc.microsoft.com) and search for CVE-2026-45465
- Download and apply the corresponding Microsoft security update for the identified SharePoint version
- After applying the update, verify the farm version matches or exceeds 16.0.19725.20384
- Test critical SharePoint workflows to ensure functionality remains intact
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45465 — 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-45465 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