CVE-2024-38094
Microsoft SharePoint Remote Code Execution Vulnerability
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. Cloudflare publishes WAF a rule written for this CVE. Such rules block the known exploit requests and buy time, but attackers can change the request to get past them, so they do not replace the patch.
Cloudflare · 1 rule (Block) · since 6 Jan 2025
Also consider: patch · enable the vendor rule in block mode · allow-list classes
Based on WAF vendor rules published for this CVE. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-38094 being exploited?
Yes. CVE-2024-38094 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-38094?
CVE-2024-38094 is rated High with a CVSS score of 7.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-38094?
Yes. A fix has been recorded for CVE-2024-38094. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-38094 affect?
CVE-2024-38094 affects microsoft:sharepoint_server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected>= 16.0.0 and < 16.0.5456.1000
- affected>= 16.0.0 and < 16.0.10412.20001
- affected>= 16.0.0 and < 16.0.17328.20424
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 22 Oct 2024 (SSVC 2.0.3).
timeline
- 9 Jul 2024Published
- 22 Oct 2024Added to CISA KEV (exploited in the wild) · 104 days (about 3 months) later
- 22 Oct 2024CISA SSVC assessment: exploitation active · 1 day later
- 12 Nov 2024CISA remediation due date (US federal agencies) · 20 days later
- 10 Feb 2026CVE record last updated · 456 days (about 1 year) later
- 2 Nov 2026Analysed by vulneraibility.com · 265 days (about 9 months) later
- Patchmsrc.microsoft.com /update-guide/vulnerability/CVE-2024-38094
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-38094
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.