dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 12 Nov 2024. Known ransomware use
Sharepoint ServerApplication · Microsoft

CVE-2024-38094

HIGH · 7.2 CVSS v3.1 Developing Published 2024-07-09
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Remotely reachable Zero-click Patch available

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 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

This is a remote code execution vulnerability in Microsoft SharePoint Server. The vulnerability allows an authenticated attacker to execute arbitrary code on the affected SharePoint server, likely through specially crafted SharePoint packages or workflows.

MitigationApply the Microsoft security update for CVE-2024-38094 as soon as possible, which is available through standard Windows Update or Microsoft Update channels.

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:all versions= 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 installed SharePoint Server version
    Open SharePoint Central Administration, go to System Settings > Manage servers in this farm, or run PowerShell command: (Get-SPFarm).BuildVersion
    Affected if Version matches SharePoint Server 2016 or 2019, or falls within the affected range of all unpatched versions
  2. Verify SharePoint Web Application is running and accessible
    Check if SharePoint web applications are started: in Central Administration > Application Management > Manage web applications, verify status is 'Started'. Alternatively, browse to your SharePoint site URLs and confirm they respond.
    Affected if SharePoint web applications are online and reachable over network
  3. Confirm authentication is enabled for SharePoint sites
    In Central Administration > Authentication Providers, verify at least one authentication method (Windows, Forms, Claims) is enabled for your web applications.
    Affected if Authentication providers are enabled, as the vulnerability requires an authenticated attacker
  4. Review farm account privileges
    Run PowerShell: Get-SPManagedAccount to list service accounts. Ensure farm service accounts follow least-privilege principles and are not unnecessarily granted domain admin or other high-privilege roles.
    Affected if Service accounts have excessive privileges that could be abused post-exploitation

Your environment is affected if you run an unpatched SharePoint Server 2016 or 2019 (or any unpatched version) with accessible web applications and authenticated user access enabled.

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
Patch available Apply the vendor patch
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply the Microsoft security update for CVE-2024-38094 as soon as possible, which is available through standard Windows Update or Microsoft Update channels.

Recommended fix High confidence

July 2024 Security Updates for SharePoint Server 2016 and 2019 (Microsoft Update Catalog)

  1. Apply the July 2024 security updates for Microsoft SharePoint Server as released by Microsoft
  2. For SharePoint Server 2016: Install the July 2024 cumulative update (CU) from the Microsoft Update Catalog
  3. For SharePoint Server 2019: Install the July 2024 security update (KB5002564 or subsequent)
  4. Verify the patch was applied successfully via SharePoint Administration Center or Windows Update
  5. Test critical SharePoint workflows after applying the update in a staging environment before production deployment
Caveat Standard SharePoint patch testing recommended; minimal risk for security-only updates

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

Fix this in Sharepoint Server Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-38094 — 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-38094 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