CVE-2025-47163
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 an insecure deserialization vulnerability in Microsoft Office SharePoint. An authenticated attacker can send specially crafted serialized data to a SharePoint server, causing code execution. The attack is remote over the network and does not require local access.
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= 2016< 16.0.18526.20396= 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 installation versionRun PowerShell command: Get-SPFarm | Select-Object BuildVersion, Version. Or check Central Administration > System Settings > Manage farm configurationAffected if Version is 2016 (any build) or 2019 with build < 16.0.18526.20396
-
Confirm SharePoint edition and server roleIn Central Administration > System Settings > Manage servers in this farm, note whether running SharePoint Server or SharePoint Enterprise ServerAffected if Running SharePoint Enterprise Server 2016 or SharePoint Server 2019
-
Check if SharePoint Web Services are exposedReview IIS Manager > Sites > SharePoint Web Services, verify which endpoints are bound to external interfaces. Run: Get-SPServiceEndpoint to list service endpointsAffected if Web services handling serialized data are accessible from untrusted networks
-
Examine ULS logs for deserialization anomaliesLocate ULS logs in C:\Program Files\Common Files\microsoft shared\Web Server Extensions\LOGS and search for terms like 'BinarySerializer', 'BinaryFormatter', 'deserialization', 'SerializationException' using Get-Content or plain text searchAffected if Logs show unexpected serialization activity or known exploitation patterns (note: post-exploitation only)
-
Review authentication configurationIn Central Administration > Application Management > Manage web applications > Authentication Providers, verify which authentication methods are enabled and whether low-privilege users can access vulnerable endpointsAffected if Authenticated users with minimal privileges can submit requests to SharePoint APIs
Environment is affected if running SharePoint Enterprise Server 2016 or SharePoint Server 2019 with build version below 16.0.18526.20396, and the server accepts authenticated user requests over the network.
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.18526.20396
Apply the latest Microsoft security patches for SharePoint immediately. Until patches are available, restrict SharePoint access to only necessary authorized users and monitor for suspicious deserialization patterns in server logs.
SharePoint Server 2019: Version 16.0.18526.20396 or later; SharePoint Server 2016: Apply May 2025 security update (KB505XX)
- Identify your current SharePoint Server version via SharePoint Administration Central > System Settings > Manage farm version
- For SharePoint Server 2019: Install Cumulative Update 16.0.18526.20396 or later from Microsoft Update Catalog
- For SharePoint Enterprise Server 2016: Install the corresponding security update for your version (KBXXXXX for CVE-2025-47163)
- After installation, run the SharePoint Products Configuration Wizard
- Verify the farm is operational and test critical workflows
- Confirm the version has been updated in Central Administration
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47163 — 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-47163 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