# CVE-2023-29357: Microsoft SharePoint Server Privilege Escalation

> An attacker can elevate privileges in Microsoft SharePoint Server, potentially gaining unauthorized access to sensitive data or system functions.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 10 Jan 2024 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2023
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-m2h6-v37r-r43p

## What is CVE-2023-29357?

CVE-2023-29357 is a critical vulnerability in Microsoft Sharepoint Server, published on 13 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Microsoft SharePoint Server Elevation of Privilege Vulnerability

Weakness: CWE-303 (Incorrect Implementation of Authentication Algorithm)

## Which versions are affected by CVE-2023-29357?

It affects 1 product.


Products: Microsoft Sharepoint Server.

## How do I fix CVE-2023-29357?

No fix has been published for CVE-2023-29357 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 31 Jan 2024.

## Is CVE-2023-29357 being exploited?

Yes. Attackers have exploited CVE-2023-29357 in the wild since at least 10 Jan 2024, including in ransomware campaigns.

Public exploit code:

- Microsoft SharePoint Server Elevation of Privilege Vulnerability (github_poc): https://github.com/Chocapikk/CVE-2023-29357
- https://github.com/LuemmelSec/CVE-2023-29357 (github_poc): https://github.com/LuemmelSec/CVE-2023-29357
- https://github.com/Guillaume-Risch/cve-2023-29357-Sharepoint (github_poc): https://github.com/Guillaume-Risch/cve-2023-29357-Sharepoint
- Recreation of the SharePoint PoC for CVE-2023-29357 in C# from LuemmelSec (github_poc): https://github.com/KeyStrOke95/CVE-2023-29357-ExE
- A Python script that verifies whether a target is vulnerable to CVE-2023-29357 or not (github_poc): https://github.com/Jev1337/CVE-2023-29357-Check
- End-to-end SOC incident analysis and threat hunting playbook targeting Microsoft SharePoint privilege escalation (CVE-2023-29357) using SIEM logs, firewall data, and threat intel. LetsDefend lab scenario (SOC227). (github_poc): https://github.com/Zedocun/Sharepoint-cve-2023-29357-incident-response

## Other vulnerabilities in Microsoft Sharepoint Server

- [CVE-2026-50522](https://insights.sbomify.com/CVE-2026-50522/): Microsoft SharePoint Deserialization of Untrusted Data Vulnerability (critical 9.8, exploited in the wild)
- [CVE-2026-58644](https://insights.sbomify.com/CVE-2026-58644/): Microsoft SharePoint Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2026-20963](https://insights.sbomify.com/CVE-2026-20963/): Microsoft SharePoint Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2025-53770](https://insights.sbomify.com/CVE-2025-53770/): Microsoft SharePoint Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2026-55040](https://insights.sbomify.com/CVE-2026-55040/): Microsoft SharePoint Weak Authentication (critical 9.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-29357 and fix it if it is affected.

What it is: CVE-2023-29357 is a critical vulnerability in Microsoft Sharepoint Server, published on 13 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2023-29357 in the wild since at least 10 Jan 2024, including in ransomware campaigns.

Affected product: Microsoft Sharepoint Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-29357/ (Markdown: https://insights.sbomify.com/CVE-2023-29357/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-29357
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-29357
- OSV: https://osv.dev/vulnerability/CVE-2023-29357

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-29357/
Summaries are generated and may contain mistakes; the official description above is the record.