CVE-2025-59228
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 input validation 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 confidenceA remote code execution vulnerability exists in Microsoft Office SharePoint due to improper input validation. An authenticated attacker can send specially crafted requests to exploit this flaw and execute arbitrary code on the SharePoint server over the network.
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.19127.20262= 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the SharePoint Server versionOpen SharePoint Central Administration, go to System Settings > Manage server in this farm, or run PowerShell: Get-SPFarm | Select-Object BuildVersionAffected if The displayed version is less than 16.0.19127.20262, indicating an unpatched installation
-
Confirm SharePoint editionCheck the installed product type in Central Administration under System Settings > Manage servers in this farm, or use PowerShell: Get-SPFarm | Select-Object ProductsAffected if The product listed is SharePoint Server 2016 or SharePoint Server 2019 (all versions of these editions are affected)
-
Verify build version numberIn Central Administration, navigate to the Farm Servers page or run PowerShell: (Get-SPFarm).BuildVersionAffected if The build version is below 16.0.19127.20262
The environment is affected if running any version of SharePoint Server 2016 or 2019, or if the SharePoint Server build version is below 16.0.19127.20262
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.19127.20262
Apply the latest Microsoft SharePoint security updates when released. Until a patch is available, restrict SharePoint access to authorized users only and monitor for suspicious input patterns in HTTP requests.
SharePoint Server 2016/2019 to build 16.0.19127.20262 or later via Microsoft security update
- Identify your current SharePoint Server build number via SharePoint Administration Central or PowerShell (Get-SPFarm).
- Determine the appropriate Microsoft security update for your SharePoint version (2016 or 2019) from msrc.microsoft.com for CVE-2025-59228.
- Download the corresponding cumulative update or security patch from the Microsoft Catalog.
- Test the patch in a non-production environment first, verifying farm functionality and any third-party solutions.
- Apply the patch during a planned maintenance window following Microsoft update procedures.
- Verify the build number has updated to 16.0.19127.20262 or later post-installation.
- Confirm SharePoint services and web applications are functioning normally.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59228 — 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-2025-59228 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