CVE-2025-30384
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 unauthorized attacker to execute code 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 confidenceThis is a deserialization vulnerability in Microsoft Office SharePoint where the application deserializes untrusted data without proper validation. An unauthenticated attacker can exploit this to execute arbitrary code on the affected SharePoint server, potentially compromising the entire SharePoint farm.
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.18526.20286= 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
- Local
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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.
-
Check SharePoint version via PowerShellRun Get-SPFarm | Select-Object BuildVersion in SharePoint Management ShellAffected if Version is below 16.0.18526.20286, or is 2016 or 2019
-
Verify SharePoint build numberOpen SharePoint Central Administration > System Settings > Manage servers in this farm, note the Build number columnAffected if Build number matches affected version range
-
Confirm SharePoint services runningRun Get-Service | Where-Object {$_.Name -like '*SharePoint*'} to list running SharePoint servicesAffected if Any SharePoint service is running on an affected version
-
Check SharePoint web applicationsRun Get-SPWebApplication to list web applications, as the vulnerability is reachable via web requestsAffected if Web applications exist on an affected SharePoint installation
If the SharePoint Server version is 2016, 2019, or below build 16.0.18526.20286, the environment is likely affected by this deserialization 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.20286
Apply the Microsoft security update for CVE-2025-30384 to all affected SharePoint servers. Until the patch is available, consider network segmentation to limit SharePoint exposure and monitor for indicators of compromise.
Install the May 2025 Security Update for SharePoint Server (build 16.0.18526.20286 or later)
- Navigate to the Microsoft Security Response Center (msrc.microsoft.com) and search for CVE-2025-30384
- Identify the applicable security update for your SharePoint Server version (2016, 2019, or Subscription Edition)
- Download and install the corresponding KB article update from Microsoft Update Catalog or through Windows Update
- After installation, verify the SharePoint Server build version matches or exceeds 16.0.18526.20286
- Restart SharePoint services and verify farm functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30384 — 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-30384 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