CVE-2025-29793
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 an authenticated attacker can exploit unsafe deserialization of data to achieve remote code execution. The attack requires the attacker to have authorized access to the SharePoint environment, but once authenticated, they can execute arbitrary code 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= 2016< 16.0.18526.20172= 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 product editionRun 'Get-SPFarm | Select-Object Products' in SharePoint Management Shell to determine if the server runs SharePoint Server or SharePoint Enterprise Server 2016 or 2019Affected if The product shows SharePoint Server 2016, SharePoint Server 2019, or SharePoint Enterprise Server 2016
-
Retrieve SharePoint build versionRun 'Get-SPFarm | Select-Object BuildVersion' in SharePoint Management Shell to obtain the exact build numberAffected if Build version is 2016 (any build) or is below 16.0.18526.20172 for SharePoint 2019
-
Check SharePoint web application authenticationRun 'Get-SPWebApplication -IncludeCentralAdministration' and review authentication providers configured. Verify that forms-based or Windows authentication is enabledAffected if Any web application accepts user authentication - the vulnerability is exploitable once an attacker has valid credentials
-
Confirm SharePoint service account exposureReview which domain accounts have SharePoint farm administrator privileges via 'Get-SPFarmAdministrator'Affected if Any user account with farm administrator rights could potentially exploit this if compromised
-
Verify SharePoint is network-accessibleCheck that SharePoint web applications are bound to network interfaces accessible from outside by reviewing IIS bindings with 'Get-WebBinding' or SharePoint Central Admin bindingsAffected if SharePoint is reachable over the network - the vulnerability can be exploited remotely by any authenticated user
You are affected if your SharePoint Server or Enterprise Server 2016 is at any build version, or if your SharePoint Server 2019 build is below 16.0.18526.20172, and the server 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.18526.20172
Apply Microsoft security updates for SharePoint as soon as they become available. Ensure SharePoint servers are fully patched and follow the principle of least privilege for user accounts.
Apply Microsoft security update for CVE-2025-29793 (check MSRC for specific KB)
- Check your current SharePoint Server build version by going to Central Administration > System Settings > Manage servers in this farm
- Navigate to Microsoft Security Response Center (msrc.microsoft.com) and search for CVE-2025-29793 to obtain the specific security update/KB article for your SharePoint version
- Apply the relevant security update for SharePoint 2016 or SharePoint 2019 as indicated in the MSRC documentation
- After patching, verify the build version matches or exceeds 16.0.18526.20172
- Test critical SharePoint workflows to ensure functionality is maintained post-update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-29793 — 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-29793 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