dbcve.org
Sharepoint ServerApplication · Microsoft

CVE-2024-30044

HIGH · 7.2 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 16.0.17328.20292 or later.
See remediation →
78/100
Remediation priority · High
High EPSS Remotely reachable 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
Microsoft SharePoint Server Remote Code Execution Vulnerability

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 · low confidence

An authenticated remote code execution vulnerability in Microsoft SharePoint Server allows attackers to execute arbitrary code by exploiting specially crafted web requests. The vulnerability requires authentication, indicating an authenticated attacker can trigger the RCE.

MitigationApply Microsoft security patches for CVE-2024-30044 to all affected SharePoint Server installations, typically through Windows Update or manual patch deployment in SharePoint farms.

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.17328.20292= 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
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 checks

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

  1. Identify SharePoint Server version
    Locate the installed SharePoint Server version using the SharePoint Administration Shell or Central Administration, typically found in the 'Farm Management' or 'System Settings' area. Record the full build number.
    Affected if The installed version is any version of SharePoint Server 2016, SharePoint Server 2019, or a version earlier than build 16.0.17328.20292.
  2. Confirm SharePoint edition
    Verify that the affected server is running Microsoft SharePoint Server (Standard or Enterprise edition) rather than SharePoint Foundation or online versions.
    Affected if The server is running SharePoint Server 2016 or 2019.
  3. Verify authentication is enabled
    Check that the SharePoint web application has authentication configured and enabled, as this vulnerability requires an authenticated attacker.
    Affected if Authentication is enabled and the server accepts user logins.
  4. Assess network exposure
    Determine if the SharePoint Server is accessible over the network (HTTP/HTTPS) from untrusted networks, since this is a remote vulnerability.
    Affected if The SharePoint web interfaces are reachable from network locations beyond the trusted internal network.
  5. Check for pending security updates
    Review the installed SharePoint updates in Windows Update history or the SharePoint patch list to identify if the security fix for CVE-2024-30044 has been applied.
    Affected if The security update for CVE-2024-30044 is not listed as installed.

You are affected if your SharePoint Server version matches 2016, 2019, or is earlier than build 16.0.17328.20292, and the server has authentication enabled with network accessibility.

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.17328.20292 or later
Fixed in 16.0.17328.20292
Interim mitigation

Apply Microsoft security patches for CVE-2024-30044 to all affected SharePoint Server installations, typically through Windows Update or manual patch deployment in SharePoint farms.

Recommended fix Moderate confidence

SharePoint Server build 16.0.17328.20292 or later (Cumulative Update containing the security fix)

  1. Identify your current SharePoint Server build version via SharePoint Administration Center or PowerShell (Get-SPFarm).
  2. Download and apply the latest SharePoint Server updates from Microsoft Update Catalog or through Windows Update.
  3. Ensure you have a full backup of the SharePoint farm databases and config before applying updates.
  4. Run the SharePoint Products Configuration Wizard (PSConfig) after installing updates to complete the upgrade process.
  5. Verify the build version has been updated to 16.0.17328.20292 or later using Get-SPFarm.
Caveat Test updates in a staging environment first as SharePoint updates may require downtime and can affect farm functionality

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-2024-30044 — 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-2024-30044 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