dbcve.org
Sharepoint ServerApplication · Microsoft

CVE-2025-29976

HIGH · 7.8 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 16.0.18526.20286 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Improper privilege management in Microsoft Office SharePoint allows an authorized attacker to elevate privileges locally.

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 confidence

This is an improper privilege management vulnerability in Microsoft Office SharePoint. An authorized attacker with existing SharePoint access can exploit the flaw to elevate their privileges locally within the SharePoint environment, gaining higher-level permissions than originally assigned.

MitigationApply the Microsoft security update for CVE-2025-29976 when released. Until then, limit SharePoint user permissions to minimum required levels and monitor for suspicious privilege escalation activities.

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
Sharepoint ServerApplication
Affected:< 16.0.18526.20286= 2016= 2019

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify SharePoint Server version
    Run 'Get-SPFarm | Select-Object BuildVersion' in SharePoint Management Shell, or check the version in SharePoint Central Administration under 'System Settings > Manage servers in this farm'
    Affected if The installed version is SharePoint Server 2016 or 2019, or any version with build number lower than 16.0.18526.20286
  2. Confirm the specific build number
    Check the exact build version in Central Administration or via PowerShell: (Get-SPFarm).BuildVersion.ToString()
    Affected if The build version is less than 16.0.18526.20286 (for newer installations) OR matches version 2016 or 2019 exactly
  3. Review SharePoint audit logs for privilege changes
    In Central Administration, go to 'Security > Review policy and permissions > Audit log reports', or use PowerShell: Search-SPLogEvent -Level High | Where-Object {$_.EventID -eq 'PermissionChange'}
    Affected if Audit logs show unexpected changes to user permissions or role assignments that were not initiated by authorized administrators
  4. Check for unauthorized role assignments
    Run 'Get-SPRoleAssignment -WebApplication' in SharePoint Management Shell to list all role assignments, or review site collection administrators via Central Administration
    Affected if Users or accounts appear with elevated permissions or site collection administrator rights that were not deliberately assigned by administrators

You are affected if your SharePoint Server installation is version 2016 or 2019, or has a build number lower than 16.0.18526.20286, AND you observe unexplained privilege escalations in your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 16.0.18526.20286 or later
Fixed in 16.0.18526.20286
Interim mitigation

Apply the Microsoft security update for CVE-2025-29976 when released. Until then, limit SharePoint user permissions to minimum required levels and monitor for suspicious privilege escalation activities.

Recommended fix Moderate confidence

SharePoint Server version 16.0.18526.20286 or later (the specific February 2024 security update for your SharePoint edition)

  1. Check the Microsoft Security Response Center (msrc.microsoft.com) for the February 2024 security updates for SharePoint Server
  2. Apply the appropriate security update for your SharePoint version (2016, 2019, or Server)
Caveat Review Microsoft documentation for any known issues or configuration changes required after applying the security update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sharepoint Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-29976 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-29976 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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