dbcve.org
Sharepoint ServerApplication · Microsoft

CVE-2025-59237

HIGH · 8.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 16.0.19127.20262 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Deserialization of untrusted data in Microsoft Office SharePoint allows an authorized attacker to execute code 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 deserialization vulnerability exists in Microsoft Office SharePoint where untrusted data is improperly handled during deserialization, allowing an authenticated attacker to execute arbitrary code remotely. This is a remote code execution (RCE) vulnerability in the SharePoint server-side application.

MitigationApply the Microsoft security patch for CVE-2025-59237 when released. Until then, restrict network access to SharePoint servers to authorized users only and monitor for suspicious deserialization activity.

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.20262= 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Identify if SharePoint Server is installed
    Check for SharePoint services running on the system. On Windows servers, open Services console (services.msc) and look for 'SharePoint' services, or run 'Get-Service | Where-Object {$_.DisplayName -like "*SharePoint*"}' in PowerShell.
    Affected if Any SharePoint service is found running on the server.
  2. Determine the installed SharePoint version
    On the SharePoint server, open SharePoint Management Shell (PowerShell) and run: (Get-SPFarm).BuildVersion.ToString(). This returns the version number in format like 16.0.x.x.
    Affected if The version returned is less than 16.0.19127.20262, or matches 16.0.1.x (SharePoint 2016) or 16.0.7.x-16.0.13.x (SharePoint 2019).
  3. Check if the server is exposed to network
    Review firewall rules and network configuration to determine if the SharePoint web applications are accessible from untrusted networks. Check IIS Manager for binding configurations on port 443/80.
    Affected if SharePoint is bound to external IP addresses or firewall allows inbound traffic from untrusted networks to SharePoint ports (80, 443, or custom ports).
  4. Verify authentication is properly restricted
    Review SharePoint authentication providers in Central Administration under 'Authentication Providers'. Ensure NTLM, Kerberos, or modern authentication is not exposed to anonymous or untrusted users.
    Affected if Anonymous authentication is enabled or authentication is not restricted to authorized domain users.

The server is affected if SharePoint Server is installed with a version below 16.0.19127.20262 (including 2016 and 2019 releases) and the server is network-accessible to authenticated attackers.

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.20262 or later
Fixed in 16.0.19127.20262
Interim mitigation

Apply the Microsoft security patch for CVE-2025-59237 when released. Until then, restrict network access to SharePoint servers to authorized users only and monitor for suspicious deserialization activity.

Recommended fix Moderate confidence

SharePoint Server 2016/2019 to build 16.0.19127.20262 or later cumulative update

  1. 1. Identify your current SharePoint Server build version in Central Administration under 'Manage servers in farm'
  2. 2. For SharePoint Server 2016, apply the latest cumulative update that includes security fix for CVE-2025-59237
  3. 3. For SharePoint Server 2019, apply the latest cumulative update that includes security fix for CVE-2025-59237
  4. 4. Download and install the security update from Microsoft Update Catalog or through Windows Server Update Services (WSUS)
  5. 5. Run the SharePoint Products Configuration Wizard (PSConfig) after applying the update
  6. 6. Verify the farm build version has been updated to 16.0.19127.20262 or higher
Caveat Test updates in staging environment before production deployment; some farm configurations may require additional post-update steps

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

Fix this in Sharepoint Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
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,864.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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