CVE-2023-24955
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 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 · moderate confidenceA remote code execution vulnerability exists in Microsoft SharePoint Server that allows authenticated attackers to execute arbitrary code on the affected server. The CVSS 7.2 score indicates a network-based attack vector with moderate attack complexity, requiring some privileges, and resulting in high impact on system availability and integrity.
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= 2016all versions= 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify SharePoint Server is installedCheck for SharePoint services or the presence of SharePoint installation directories on the server (typically in C:\Program Files\Microsoft Office Servers or via Get-Service in PowerShell for SharePoint related services)Affected if SharePoint Server is found to be installed on the system
-
Identify the installed SharePoint versionRun the SharePoint Management Shell command 'Get-SPFarm | Select-Object BuildVersion' or check the SharePoint version through Windows Programs and FeaturesAffected if The installed version matches Microsoft SharePoint Enterprise Server 2016 or Microsoft SharePoint Server 2019, or is an older version that falls within the affected range
-
Confirm network accessibility of SharePointVerify that the SharePoint web application ports (typically 80, 443, or custom ports) are listening and accessible from network locationsAffected if SharePoint is reachable over the network, which is required for the network-based attack vector
-
Verify SharePoint authentication is enabledCheck that SharePoint is configured to accept authenticated connections (standard SharePoint behavior for web applications)Affected if Anonymous orForms-based authentication is not the only authentication method in use, as the vulnerability requires authenticated attacker access
A system is affected if it runs any version of Microsoft SharePoint Server (particularly 2016 or 2019) and is accessible over a network where unauthenticated or low-privilege attackers could potentially authenticate to the SharePoint environment.
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 the relevant Microsoft security updates for SharePoint Server to address this vulnerability. Prioritize patching for internet-facing SharePoint installations.
- Check the Microsoft Security Response Center (msrc.microsoft.com) for CVE-2023-24955 to identify the specific KB article for your SharePoint version
- For SharePoint Server 2019, apply the corresponding security update from the May 2023 or June 2023 patch cycle
- For SharePoint Enterprise Server 2016, apply the corresponding security update from the May 2023 or June 2023 patch cycle
- Verify the patch was successfully installed by checking the installed updates on the SharePoint server
- Test critical SharePoint workflows after applying the update to ensure functionality
- Review CISA guidance at www.cisa.gov for any additional hardening recommendations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-24955 — 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-2023-24955 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