CVE-2025-54897
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 · uneditedDeserialization 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 confidenceThis is a deserialization vulnerability in Microsoft Office SharePoint where the software deserializes data without proper validation. An attacker with authorized access to SharePoint can send specially crafted serialized objects that, when deserialized, allow arbitrary code execution on the affected server.
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.20100= 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 SharePoint Server versionOpen SharePoint Management Shell and run: Get-SPFarm | Select-Object BuildVersionAffected if Version matches 2016, 2019, or is earlier than 16.0.19127.20100
-
Verify exact build numberIn SharePoint Central Administration, go to System Settings > Manage servers in this farm. Note the Configuration Database Version.Affected if Build number is less than 16.0.19127.20100 (for any version branch)
-
Confirm SharePoint editionRun: (Get-SPFarm).Products to list installed SharePoint productsAffected if Output contains 'Microsoft SharePoint Server 2016' or 'Microsoft SharePoint Server 2019'
-
Check for serialized data processing featuresReview SharePoint workflows, InfoPath forms, or any custom solutions that accept serialized objects. Inspect web.config files for serialized data handlers.Affected if Any feature handling deserialized objects is in use without additional validation layers
A system is affected if it runs SharePoint Server 2016 or 2019, or any version with build number below 16.0.19127.20100, AND has features that process serialized data accessible to authorized users.
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.20100
Apply the latest Microsoft SharePoint security updates immediately. Since this requires authorized access, also review and minimize the number of users with elevated SharePoint privileges and monitor for suspicious activity.
SharePoint Server version 16.0.19127.20100 or later (apply the corresponding security update for SharePoint 2016 or 2019 from Microsoft)
- 1. Review the Microsoft Security Response Center (msrc.microsoft.com) for CVE-2025-54897 to obtain the specific security update/fix for your SharePoint Server version
- 2. Identify your current SharePoint Server version (2016, 2019, or other) using SharePoint Administration Center or PowerShell Get-SPFarm | Select BuildVersion
- 3. Download and install the appropriate security update from Microsoft Update Catalog or through Windows Update
- 4. Run the SharePoint Products Configuration Wizard (psconfig.exe) after applying the update
- 5. Verify the version has been updated to 16.0.19127.20100 or later by checking the build version
- 6. Test critical SharePoint workflows and workflows dependent on custom solutions that may use serialization
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54897 — 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-54897 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