CVE-2025-62204
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 processing untrusted serialized data allows an authenticated attacker to achieve remote code execution over the network. The attacker requires valid authorization credentials to exploit this flaw.
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.20338= 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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.
-
Determine SharePoint Server versionOpen SharePoint Management Shell and run: (Get-SPFarm).BuildVersion or check Central Administration > System Settings > Manage server in this farmAffected if The version number is lower than 16.0.19127.20338, or matches 16.0.x for SharePoint 2016 or 2019 (these are also affected)
-
Identify SharePoint build editionIn Central Administration, go to System Settings > Manage servers in this farm. Note the SKU and version columnsAffected if The product is SharePoint Server 2016 or 2019, regardless of build version, as these specific releases are explicitly listed as affected
-
Verify authentication is enabled for SharePoint web applicationsCheck Central Administration > Application Management > Manage web applications. Confirm which authentication methods (Classic or Claims) are enabled for each web applicationAffected if Any web application accepts user authentication, as the vulnerability requires valid credentials to exploit the deserialization flaw
-
Confirm presence of custom or third-party deserialization handlersReview web.config files in the SharePoint web root for custom ISerializable implementations or BinaryFormatter usage, and check ISAPI filters or custom web service endpointsAffected if Non-Microsoft deserialization handlers or BinaryFormatter deserialization is configured, as these provide the attack vector for RCE
-
Audit SharePoint service accounts privilegesReview service account permissions in Central Administration > Security > Configure service accounts. Check which accounts run Microsoft SharePoint Foundation Web Application serviceAffected if Service accounts have excessive privileges (such as local admin or db_owner) beyond what the principle of least privilege requires
Your environment is affected if you run any version of SharePoint Server 2016 or 2019, or if your SharePoint Server build is below 16.0.19127.20338, and your SharePoint farm accepts authenticated user connections.
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.20338
Apply Microsoft security patches for SharePoint when available; restrict network access to SharePoint servers to authorized users only; follow least-privilege principles for SharePoint service accounts.
Any SharePoint Server version with build number >= 16.0.19127.20338
- Identify your current SharePoint Server version via SharePoint Administration Central or PowerShell (Get-SPFarm).
- For SharePoint Server 2016 and 2019, apply the relevant cumulative update (CU) that includes the security fix for CVE-2025-62204.
- Verify the build number after patching matches or exceeds 16.0.19127.20338.
- Test the update in a staging environment before deploying to production.
- Schedule the update during a maintenance window to minimize business impact.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62204 — 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-62204 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