Microsoft SharePoint Server Elevation of Privilege Vulnerability
CVE-2023-29357
Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2024-01-10), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 99(Act)EG Risk 99/100SSVC: Act
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation100% × 40%Automatability100% × 15%Action: Fix now — active exploitation, automatable, high impact. - EPSS PROB
- 100%
- EPSS %ILE
- 100%
- KEV
- ⚠ Exploited
Published
June 14, 2023
Last Modified
October 28, 2025
Advisory Details (2)
Auto-updated Sep 17, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-29357Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-29357Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 92× in last 7d / 387× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 1,405 total refreshes for this CVE.
- 2026-09-19 10:39 UTCVendor advisory
- 2026-09-19 10:39 UTCGHSA enrichment
- 2026-09-19 06:52 UTCVendor advisory
- 2026-09-19 06:52 UTCGHSA enrichment
- 2026-09-19 03:06 UTCVendor advisory
- 2026-09-19 03:06 UTCGHSA enrichment
- 2026-09-18 23:20 UTCVendor advisory
- 2026-09-18 23:20 UTCGHSA enrichment
- 2026-09-18 19:34 UTCVendor advisory
- 2026-09-18 19:34 UTCGHSA enrichment
- 2026-09-18 19:20 UTCCISA KEV update
- 2026-09-18 15:48 UTCVendor advisory
- 2026-09-18 15:47 UTCGHSA enrichment
- 2026-09-18 14:15 UTCCISA KEV update
- 2026-09-18 11:58 UTCVendor advisory
- 2026-09-18 11:58 UTCGHSA enrichment
- 2026-09-18 08:12 UTCVendor advisory
- 2026-09-18 08:12 UTCGHSA enrichment
- 2026-09-18 04:26 UTCVendor advisory
- 2026-09-18 04:26 UTCGHSA enrichment
- 2026-09-18 00:40 UTCVendor advisory
- 2026-09-18 00:40 UTCGHSA enrichment
- 2026-09-17 20:54 UTCVendor advisory
- 2026-09-17 20:54 UTCGHSA enrichment
- 2026-09-17 17:08 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-17 17:08 UTCGHSA enrichment
- 2026-09-17 13:18 UTCVendor advisory
- 2026-09-17 13:18 UTCGHSA enrichment
- 2026-09-17 09:32 UTCVendor advisory
- 2026-09-17 09:32 UTCGHSA enrichment
- 2026-09-17 05:46 UTCVendor advisory
- 2026-09-17 05:45 UTCGHSA enrichment
- 2026-09-17 01:58 UTCVendor advisory
- 2026-09-17 01:58 UTCGHSA enrichment
- 2026-09-16 22:12 UTCVendor advisory
- 2026-09-16 22:12 UTCGHSA enrichment
- 2026-09-16 18:26 UTCVendor advisory
- 2026-09-16 18:26 UTCGHSA enrichment
- 2026-09-16 14:40 UTCVendor advisory
- 2026-09-16 14:40 UTCGHSA enrichment
- 2026-09-16 14:10 UTCCISA KEV update
- 2026-09-16 10:54 UTCVendor advisory
- 2026-09-16 10:53 UTCGHSA enrichment
- 2026-09-16 07:08 UTCVendor advisory
- 2026-09-16 07:08 UTCGHSA enrichment
- 2026-09-16 03:22 UTCVendor advisory
- 2026-09-16 03:22 UTCGHSA enrichment
- 2026-09-15 23:34 UTCVendor advisory
- 2026-09-15 23:34 UTCGHSA enrichment
- 2026-09-15 19:48 UTCVendor advisory
- 2026-09-15 19:48 UTCGHSA enrichment
- 2026-09-15 16:02 UTCVendor advisory
- 2026-09-15 16:01 UTCGHSA enrichment
- 2026-09-15 12:16 UTCVendor advisory
- 2026-09-15 12:16 UTCGHSA enrichment
- 2026-09-15 08:30 UTCVendor advisory
- 2026-09-15 08:30 UTCGHSA enrichment
- 2026-09-15 04:44 UTCVendor advisory
- 2026-09-15 04:43 UTCGHSA enrichment
- 2026-09-15 00:55 UTCVendor advisory
- 2026-09-15 00:55 UTCGHSA enrichment
- 2026-09-14 21:09 UTCVendor advisory
- 2026-09-14 21:09 UTCGHSA enrichment
- 2026-09-14 19:24 UTCCISA KEV update
- 2026-09-14 17:23 UTCVendor advisory
- 2026-09-14 17:23 UTCGHSA enrichment
- 2026-09-14 13:37 UTCVendor advisory
- 2026-09-14 13:37 UTCGHSA enrichment
- 2026-09-14 09:51 UTCVendor advisory
- 2026-09-14 09:50 UTCGHSA enrichment
- 2026-09-14 06:02 UTCVendor advisory
- 2026-09-14 06:02 UTCGHSA enrichment
- 2026-09-14 02:16 UTCVendor advisory
- 2026-09-14 02:16 UTCGHSA enrichment
- 2026-09-13 22:31 UTCVendor advisory
- 2026-09-13 22:31 UTCGHSA enrichment
- 2026-09-13 18:45 UTCVendor advisory
- 2026-09-13 18:45 UTCGHSA enrichment
- 2026-09-13 14:59 UTCVendor advisory
- 2026-09-13 14:59 UTCGHSA enrichment
- 2026-09-13 11:13 UTCVendor advisory
- 2026-09-13 11:13 UTCGHSA enrichment
- 2026-09-13 07:26 UTCVendor advisory
- 2026-09-13 07:26 UTCGHSA enrichment
- 2026-09-13 03:41 UTCVendor advisory
- 2026-09-13 03:41 UTCGHSA enrichment
- 2026-09-12 23:55 UTCVendor advisory
- 2026-09-12 23:55 UTCGHSA enrichment
- 2026-09-12 20:09 UTCVendor advisory
- 2026-09-12 20:09 UTCGHSA enrichment
- 2026-09-12 16:23 UTCVendor advisory
- 2026-09-12 16:23 UTCGHSA enrichment
- 2026-09-12 12:37 UTCVendor advisory
- 2026-09-12 12:37 UTCGHSA enrichment
- 2026-09-12 08:51 UTCVendor advisory
- 2026-09-12 08:51 UTCGHSA enrichment
- 2026-09-12 05:05 UTCVendor advisory
- 2026-09-12 05:05 UTCGHSA enrichment
- 2026-09-12 01:19 UTCVendor advisory
- 2026-09-12 01:19 UTCGHSA enrichment
Publicly available exploits
(6 references)Working exploit code is in the public domain (1 Metasploit module) (4 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Open source ↗GitHub PoCGuillaume-Risch/cve-2023-29357-SharepointFirst seen Dec 22, 2023
- GitHub PoCKeyStrOke95/CVE-2023-29357-ExEFirst seen Oct 10, 2023
Recreation of the SharePoint PoC for CVE-2023-29357 in C# from LuemmelSec
Open source ↗ - Open source ↗GitHub PoCLuemmelSec/CVE-2023-29357First seen Sep 30, 2023
- GitHub PoCChocapikk/CVE-2023-29357First seen Sep 26, 2023
Microsoft SharePoint Server Elevation of Privilege Vulnerability
Open source ↗ - Metasploitexploit/windows/http/sharepoint_dynamic_proxy_generator_auth_bypass_rce✓ verifiedFirst seen May 1, 2023
Sharepoint Dynamic Proxy Generator Unauth RCE
Open source ↗ - Nucleihttp/cves/2023/CVE-2023-29357.yamlFirst seen Jan 1, 2023
Microsoft SharePoint - Authentication Bypass
Open source ↗
Frequently asked(6)
What is CVE-2023-29357?
When was CVE-2023-29357 disclosed?
Is CVE-2023-29357 actively exploited?
What is the CVSS score of CVE-2023-29357?
Which products are affected by CVE-2023-29357?
How do I remediate CVE-2023-29357?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2023-29357
Is Your Infrastructure Affected by CVE-2023-29357?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.