CVE-2024-49070
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 · uneditedMicrosoft 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 · moderate confidenceThis is a remote code execution vulnerability in Microsoft SharePoint Server. An authenticated attacker could potentially execute arbitrary code on affected SharePoint servers by sending specially crafted requests. The CVSS 7.4 score indicates high severity with network-exploitable attack vector and moderate attack complexity.
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 dataall versions= 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:N/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.
-
Identify SharePoint Server installationOpen SharePoint Management Shell and run: Get-SPFarm | Select-Object BuildVersion, Version, ProductsAffected if The Products field shows Microsoft SharePoint Server 2016 or 2019, or BuildVersion starts with 16.0 (indicating SharePoint 2016/2019)
-
Check Windows Registry for exact SharePoint versionOpen Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Office\Server\16.0\BuildVersion (for 2016/2019)Affected if The BuildVersion value exists and corresponds to SharePoint 2016 or 2019 release builds
-
Verify SharePoint services are runningOpen Services console (services.msc) and check if 'SharePoint Timer Service' and 'SharePoint Administration' services are running, or run Get-Service | Where-Object {$_.DisplayName -like '*SharePoint*'}Affected if SharePoint services are running, indicating an active SharePoint deployment that could receive malicious requests
-
Check SharePoint web application exposureOpen SharePoint Central Administration > Application Management > Manage web applications. Review which web applications are configured and their URLsAffected if Any SharePoint web applications are published and accessible on the network (even internally), as the vulnerability is network-exploitable
Your environment is affected if SharePoint Server 2016 or 2019 is installed and SharePoint web services are accessible on the network, regardless of authentication method.
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 · scopedApply Microsoft security updates for SharePoint Server as soon as possible. Restrict SharePoint server exposure to untrusted networks and follow least-privilege principles for SharePoint service accounts.
- 1. Check Microsoft's Security Update Guide (msrc.microsoft.com) for CVE-2024-49070
- 2. Identify the specific KB article for your SharePoint Server version (2016 or 2019)
- 3. Download and apply the corresponding security update from Microsoft Update Catalog
- 4. Run the SharePoint Products Configuration Wizard (psconfig.exe) after applying the update
- 5. Verify the patch was installed successfully via SharePoint Central Administration > Upgrade and Migration > Check product and patch installation status
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-2024-49070 — 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-2024-49070 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