Microsoft Outlook Elevation of Privilege Vulnerability
CVE-2023-23397
Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2023-03-14), 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
- 84(Attend)EG Risk 84/100SSVC: Attend
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%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 97%
- EPSS %ILE
- 100%
- KEV
- ⚠ Exploited
Published
March 14, 2023
Last Modified
June 17, 2026
Advisory Details (2)
Auto-updated Sep 7, 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-23397Security 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-23397Weakness Classification(2)
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 89× in last 7d / 366× 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,200 total refreshes for this CVE.
- 2026-09-08 22:10 UTCVendor advisory
- 2026-09-08 22:10 UTCGHSA enrichment
- 2026-09-08 18:54 UTCCISA KEV update
- 2026-09-08 18:08 UTCVendor advisory
- 2026-09-08 18:08 UTCGHSA enrichment
- 2026-09-08 14:02 UTCVendor advisory
- 2026-09-08 14:02 UTCGHSA enrichment
- 2026-09-08 09:56 UTCVendor advisory
- 2026-09-08 09:55 UTCGHSA enrichment
- 2026-09-08 05:51 UTCVendor advisory
- 2026-09-08 05:51 UTCGHSA enrichment
- 2026-09-08 01:46 UTCVendor advisory
- 2026-09-08 01:46 UTCGHSA enrichment
- 2026-09-07 21:43 UTCVendor advisory
- 2026-09-07 21:43 UTCGHSA enrichment
- 2026-09-07 17:40 UTCVendor advisory
- 2026-09-07 17:40 UTCGHSA enrichment
- 2026-09-07 13:37 UTCVendor advisory
- 2026-09-07 13:36 UTCGHSA enrichment
- 2026-09-07 09:30 UTCVendor advisory
- 2026-09-07 09:30 UTCGHSA enrichment
- 2026-09-07 05:26 UTCVendor advisory
- 2026-09-07 05:26 UTCGHSA enrichment
- 2026-09-07 01:20 UTCVendor advisory
- 2026-09-07 01:20 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-09-06 21:18 UTCVendor advisory
- 2026-09-06 21:18 UTCGHSA enrichment
- 2026-09-06 17:15 UTCEG score recompute
- 2026-09-06 17:15 UTCVendor advisory
- 2026-09-06 17:15 UTCGHSA enrichment
- 2026-09-06 13:45 UTCEPSS rescore
- 2026-09-06 13:11 UTCVendor advisory
- 2026-09-06 13:11 UTCGHSA enrichment
- 2026-09-06 09:08 UTCVendor advisory
- 2026-09-06 09:08 UTCGHSA enrichment
- 2026-09-06 05:01 UTCVendor advisory
- 2026-09-06 05:01 UTCGHSA enrichment
- 2026-09-06 00:58 UTCVendor advisory
- 2026-09-06 00:58 UTCGHSA enrichment
- 2026-09-05 20:53 UTCVendor advisory
- 2026-09-05 20:53 UTCGHSA enrichment
- 2026-09-05 16:50 UTCEG score recompute
- 2026-09-05 16:50 UTCVendor advisory
- 2026-09-05 16:49 UTCGHSA enrichment
- 2026-09-05 15:25 UTCEPSS rescore
- 2026-09-05 12:43 UTCVendor advisory
- 2026-09-05 12:43 UTCGHSA enrichment
- 2026-09-05 08:40 UTCVendor advisory
- 2026-09-05 08:40 UTCGHSA enrichment
- 2026-09-05 04:37 UTCVendor advisory
- 2026-09-05 04:37 UTCGHSA enrichment
- 2026-09-05 00:33 UTCVendor advisory
- 2026-09-05 00:33 UTCGHSA enrichment
- 2026-09-04 20:29 UTCVendor advisory
- 2026-09-04 20:29 UTCGHSA enrichment
- 2026-09-04 17:38 UTCCISA KEV update
- 2026-09-04 16:24 UTCVendor advisory
- 2026-09-04 16:24 UTCGHSA enrichment
- 2026-09-04 12:21 UTCVendor advisory
- 2026-09-04 12:21 UTCGHSA enrichment
- 2026-09-04 08:18 UTCVendor advisory
- 2026-09-04 08:18 UTCGHSA enrichment
- 2026-09-04 04:16 UTCVendor advisory
- 2026-09-04 04:16 UTCGHSA enrichment
- 2026-09-04 00:12 UTCVendor advisory
- 2026-09-04 00:12 UTCGHSA enrichment
- 2026-09-03 20:06 UTCVendor advisory
- 2026-09-03 20:06 UTCGHSA enrichment
- 2026-09-03 16:02 UTCVendor advisory
- 2026-09-03 16:02 UTCGHSA enrichment
- 2026-09-03 11:58 UTCVendor advisory
- 2026-09-03 11:58 UTCGHSA enrichment
- 2026-09-03 07:52 UTCVendor advisory
- 2026-09-03 07:51 UTCGHSA enrichment
- 2026-09-03 03:45 UTCVendor advisory
- 2026-09-03 03:45 UTCGHSA enrichment
- 2026-09-02 23:41 UTCVendor advisory
- 2026-09-02 23:41 UTCGHSA enrichment
- 2026-09-02 19:39 UTCVendor advisory
- 2026-09-02 19:38 UTCGHSA enrichment
- 2026-09-02 17:33 UTCCISA KEV update
- 2026-09-02 15:34 UTCVendor advisory
- 2026-09-02 15:34 UTCGHSA enrichment
- 2026-09-02 11:30 UTCVendor advisory
- 2026-09-02 11:29 UTCGHSA enrichment
- 2026-09-02 07:26 UTCVendor advisory
- 2026-09-02 07:25 UTCGHSA enrichment
- 2026-09-02 03:22 UTCVendor advisory
- 2026-09-02 03:22 UTCGHSA enrichment
- 2026-09-01 23:18 UTCVendor advisory
- 2026-09-01 23:18 UTCGHSA enrichment
- 2026-09-01 19:15 UTCVendor advisory
- 2026-09-01 19:15 UTCGHSA enrichment
- 2026-09-01 15:08 UTCVendor advisory
- 2026-09-01 15:08 UTCGHSA enrichment
- 2026-09-01 11:04 UTCVendor advisory
- 2026-09-01 11:04 UTCGHSA enrichment
- 2026-09-01 07:01 UTCVendor advisory
- 2026-09-01 07:01 UTCGHSA enrichment
- 2026-09-01 02:57 UTCVendor advisory
Publicly available exploits
(10 references)Working exploit code is in the public domain (10 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCPushkarup/CVE-2023-23397First seen Oct 26, 2023
This script exploits CVE-2023-23397, a Zero-Day vulnerability in Microsoft Outlook, allowing the generation of malicious emails for testing and educational purposes.
Open source ↗ - Open source ↗GitHub PoCMuhammad-Ali007/OutlookNTLM_CVE-2023-23397First seen Jul 14, 2023
- GitHub PoCvlad-a-man/CVE-2023-23397First seen May 7, 2023
CVE-2023-23397 PoC
Open source ↗ - GitHub PoCBronzeBee/cve-2023-23397First seen Mar 22, 2023
Python script for sending e-mails with CVE-2023-23397 payload using SMTP
Open source ↗ - GitHub PoCtiepologian/CVE-2023-23397First seen Mar 21, 2023
Proof of Concept for CVE-2023-23397 in Python
Open source ↗ - GitHub PoCTrackflaw/CVE-2023-23397First seen Mar 20, 2023
Simple PoC of the CVE-2023-23397 vulnerability with the payload sent by email.
Open source ↗ - Open source ↗GitHub PoCdjackreuter/CVE-2023-23397-PoCFirst seen Mar 18, 2023
- GitHub PoCBillSkiCO/CVE-2023-23397_EXPLOITFirst seen Mar 17, 2023
Generates meeting requests taking advantage of CVE-2023-23397. This requires the outlook thick client to send.
Open source ↗ - Open source ↗GitHub PoCapi0cradle/CVE-2023-23397-POC-PowershellFirst seen Mar 16, 2023
- GitHub PoCka7ana/CVE-2023-23397First seen Mar 16, 2023
Simple PoC in PowerShell for CVE-2023-23397
Open source ↗
Frequently asked(6)
What is CVE-2023-23397?
When was CVE-2023-23397 disclosed?
Is CVE-2023-23397 actively exploited?
What is the CVSS score of CVE-2023-23397?
Which products are affected by CVE-2023-23397?
How do I remediate CVE-2023-23397?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2023-23397
Is Your Infrastructure Affected by CVE-2023-23397?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.