Sharepoint ServerApplication · Microsoft

CVE-2025-64672

CRITICAL · 9.0 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 16.0.19127.20378 or later.
See remediation →
94/100
Remediation priority · Urgent
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

A cross-site scripting (XSS) vulnerability in Microsoft Office SharePoint allows an authenticated attacker to inject malicious scripts into web pages, enabling session hijacking and credential theft through spoofing attacks.

MitigationApply Microsoft SharePoint security patches when available; implement input validation and output encoding for user-supplied content in 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.19127.20378

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

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 Central Administration, go to _admin/FarmTopology.aspx, or run PowerShell: (Get-SPFarm).BuildVersion
    Affected if Version number is lower than 16.0.19127.20378
  2. Confirm SharePoint Server edition
    Verify the installation is Microsoft SharePoint Server (not SharePoint Foundation). Check via Central Administration > System Settings > Manage servers in this farm, or via PowerShell: (Get-SPWebApplication -IncludeCentralAdministration).Url
    Affected if Running Microsoft SharePoint Server (standard or enterprise) with vulnerable version
  3. Identify web-facing pages and web parts
    Review active SharePoint sites and web parts that accept user-supplied content: list fields, discussion boards, wiki pages, custom web parts, and forms. Use PowerShell: Get-SPWebApplication | Get-SPSite -Limit All | Get-SPWeb -Limit All | Select-Object URL,AllowUnsafeUpdates
    Affected if Pages or web parts that accept user input are published and accessible to authenticated users

You are affected if your SharePoint Server version is below 16.0.19127.20378 AND you have web parts or pages that accept user input visible to authenticated users.

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.19127.20378 or later
Fixed in 16.0.19127.20378
Interim mitigation

Apply Microsoft SharePoint security patches when available; implement input validation and output encoding for user-supplied content in SharePoint pages and web parts.

Recommended fix Moderate confidence

SharePoint Server 16.0.19127.20378 or later

  1. 1. Review the Microsoft SharePoint Server requirements and compatibility for version 16.0.19127.20378
  2. 2. Backup the SharePoint farm configuration and content databases
  3. 3. Download the latest SharePoint Server updates from the Microsoft Update Catalog or Volume Licensing Service Center
  4. 4. Install the update on all SharePoint servers in the farm, starting with the application servers
  5. 5. Run the SharePoint Products Configuration Wizard on each server
  6. 6. Verify the farm is operational and test critical workflows
  7. 7. Confirm the installed version is 16.0.19127.20378 or later using SharePoint Administration Center
Caveat Review Microsoft documentation for any configuration or workflow changes required after applying this security update

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-2025-64672 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64672 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