dbcve.org
Sharepoint ServerApplication · Microsoft

CVE-2026-45462

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, potentially enabling session hijacking, credential theft, or spoofing of other users.

MitigationApply Microsoft SharePoint security updates when released; implement input validation and output encoding as compensating controls until patch deployment.

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 installed SharePoint Server version
    Open SharePoint Management Shell and run: (Get-SPFarm).BuildVersion or check in Central Administration > System Settings > Manage servers in this farm
    Affected if Version is below 16.0.19725.20384, or the version displays as 2016 or 2019 (regardless of build)
  2. Confirm SharePoint edition is Server (not Online)
    Run: Get-SPWebApplication | Select-Object Url, Type. Ensure the Type indicates on-premises SharePoint Server
    Affected if Running on-premises SharePoint Server (not SharePoint Online)
  3. Identify web parts or pages that render user-supplied content
    Review custom or third-party web parts, discussion boards, announcements, or any page that displays user input without custom encoding. Check SharePoint Designer or review custom solutions deployed
    Affected if Any web part, list view, or page displays user-provided content that could be rendered in HTML context
  4. Check if farm is fully patched for all SharePoint cumulative updates
    In Central Administration > System Settings > Check product and farm patch status, or run: Get-SPProduct -Server 'ServerName'
    Affected if Farm shows pending updates or missing SharePoint security patches

You are affected if running SharePoint Server 2016 or 2019, or any version prior to 16.0.19725.20384, and the farm renders user-supplied content in web pages.

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 SharePoint security updates when released; implement input validation and output encoding as compensating controls until patch deployment.

Recommended fix Moderate confidence

SharePoint Server 2016/2019 with security update applied to reach version 16.0.19725.20384 or later

  1. Identify the current SharePoint Server version by navigating to SharePoint Central Administration > System Settings > Manage servers in this farm
  2. Download the applicable security update from Microsoft Update Catalog or Microsoft Download Center - search for the KB article corresponding to CVE-2026-45462
  3. Apply the security update to all SharePoint servers in the farm, following Microsoft's standard update deployment procedures
  4. Run the SharePoint Products Configuration Wizard (PSConfig) on all servers after applying the update
  5. Verify the version has been updated to 16.0.19725.20384 or later by checking the farm version in Central Administration

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
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
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,192.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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