CVE-2025-29794
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 authorization 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 confidenceImproper authorization vulnerability in Microsoft Office SharePoint enables an authenticated attacker to bypass authorization checks and execute arbitrary code remotely. The attacker must have valid credentials (be 'authorized') but can exploit broken authorization logic to achieve remote code execution.
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
- 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 product and versionOpen SharePoint Central Administration > System Settings > Manage servers in this farm. Note the 'Configuration' version shown, or run 'Get-SPFarm | Select-Object BuildVersion' in SharePoint Management Shell.Affected if The version displayed matches SharePoint 2016, SharePoint 2019, or any version lower than 16.0.18526.20172
-
Confirm SharePoint editionIn Central Administration > System Settings > Manage servers in this farm, check the 'Server' column to identify if this is SharePoint Server or SharePoint Enterprise Server.Affected if The edition is SharePoint Enterprise Server 2016 or SharePoint Server 2019
-
Verify version number against thresholdCompare the exact Configuration version number from step 1 to the vulnerable threshold 16.0.18526.20172. Note that the '=' operator in the advisory means any version at or below 16.0.18526.20172 is affected.Affected if The version number is less than 16.0.18526.20172, or exactly equals 16.0.18526.20172 for SharePoint 2019, or is SharePoint 2016 (any build)
-
Check for external network exposureDetermine if the SharePoint server is directly accessible from untrusted networks. Review firewall rules, load balancer configurations, or VPN policies that govern access to SharePoint web applications.Affected if The SharePoint server is accessible over the network without strong authentication gating or network segmentation, enabling a remote attacker with valid SharePoint credentials to reach the vulnerable endpoint
A SharePoint 2016, SharePoint 2019, or any SharePoint Server version below 16.0.18526.20172 that is network-accessible to authenticated users is affected by this authorization bypass vulnerability.
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 the Microsoft security update for CVE-2025-29794 to all affected SharePoint installations. Review Microsoft SharePoint Server security bulletins and ensure all security patches are current.
SharePoint Server 2016/2019 May 2025 Cumulative Update (or latest subsequent CU)
- Check current SharePoint Server version via SharePoint Administration Central or PowerShell (Get-SPFarm | Select-Object BuildVersion)
- For SharePoint Server 2016: Install the May 2025 Cumulative Update (or latest available)
- For SharePoint Server 2019: Install the May 2025 Cumulative Update (or latest available) that includes the fix for CVE-2025-29794
- After installation, run the SharePoint Products Configuration Wizard to apply updates
- Verify the version has been updated to 16.0.18526.20172 or later
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-29794 — 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-29794 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