dbcve.org
Sharepoint ServerApplication · Microsoft

CVE-2026-45468

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 where improper input neutralization during web page generation allows an authenticated attacker to inject malicious scripts into web pages, enabling spoofing attacks against other users.

MitigationApply the appropriate Microsoft security update for SharePoint when released, and implement output encoding and input validation as defense-in-depth measures.

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
    Run 'Get-SPFarm' cmdlet in SharePoint Management Shell to retrieve the farm build version, or check Central Administration > System Settings > Manage farm configuration
    Affected if Version is below 16.0.19725.20384, or matches versions 2016 or 2019 exactly (meaning unpatched)
  2. Identify SharePoint edition
    Run 'Get-SPFarm | Select-Object BuildVersion, Version' or check Central Administration > About SharePoint to confirm the specific product (2016, 2019, or newer)
    Affected if Edition is SharePoint Server 2016 or 2019 with no patches applied
  3. Verify if patches are applied
    In Windows Server, open Programs and Features > View installed updates, or run 'Get-SPProduct -Server <ServerName>' in SharePoint Management Shell to list installed software patches
    Affected if No security updates corresponding to CVE-2026-45468 are installed, leaving the version in the vulnerable range

You are affected if your SharePoint Server installation is version 2016 or 2019, or any version below 16.0.19725.20384, and does not have the specific security patch for this XSS vulnerability installed.

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 appropriate Microsoft security update for SharePoint when released, and implement output encoding and input validation as defense-in-depth measures.

Recommended fix Moderate confidence

SharePoint Server 2019: upgrade to version 16.0.19725.20384 or later; SharePoint Server 2016: upgrade to latest cumulative update containing the CVE-2026-45468 fix

  1. 1. Review the official Microsoft Security Response Center (MSRC) advisory for CVE-2026-45468 at msrc.microsoft.com for complete patch information.
  2. 2. Identify your current SharePoint Server version via SharePoint Administration Center or PowerShell: (Get-SPFarm).BuildVersion
  3. 3. For SharePoint Server 2016, upgrade to the latest cumulative update that includes the security fix for this vulnerability.
  4. 4. For SharePoint Server 2019, upgrade to version 16.0.19725.20384 or later, which contains the fix.
  5. 5. After applying the update, verify the version has been successfully updated and test critical SharePoint workflows.
  6. 6. Monitor MSRC for any additional guidance or subsequent updates.
Caveat Standard SharePoint update risks apply - test in staging environment before production deployment; some farm configurations may require additional post-update configuration

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sharepoint Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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