CVE-2023-23397

CRITICALNVD 9.89.8—
EchelonGraph scoreHIGH confidence

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.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
9.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 97%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Microsoft Outlook Elevation of Privilege Vulnerability

CVSS v3
9.8
EG Score
9.8(high)
EPSS
99.9%
KEV
⚠ Exploited

Published

March 14, 2023

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Jun 1, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: microsoft, cisa.
cisa Patch Available🔴 Active Exploitation

Known 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-23397
microsoft Patch Available

Security 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-23397

Weakness 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 85× in last 7d / 369× 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 645 total refreshes for this CVE.

  1. 2026-07-22 20:10 UTCGHSA enrichment
  2. 2026-07-22 19:40 UTCCISA KEV update
  3. 2026-07-22 16:07 UTCVendor advisory
  4. 2026-07-22 16:07 UTCGHSA enrichment
  5. 2026-07-22 12:01 UTCVendor advisory
  6. 2026-07-22 12:01 UTCGHSA enrichment
  7. 2026-07-22 07:57 UTCVendor advisory
  8. 2026-07-22 07:57 UTCGHSA enrichment
  9. 2026-07-22 03:54 UTCVendor advisory
  10. 2026-07-22 03:54 UTCGHSA enrichment
  11. 2026-07-21 23:44 UTCVendor advisory
  12. 2026-07-21 23:44 UTCGHSA enrichment
  13. 2026-07-21 19:14 UTCEG score recompute
  14. 2026-07-21 19:14 UTCVendor advisory
  15. 2026-07-21 19:14 UTCGHSA enrichment
  16. 2026-07-21 15:23 UTCEPSS rescore
  17. 2026-07-21 15:10 UTCVendor advisory
  18. 2026-07-21 15:09 UTCGHSA enrichment
  19. 2026-07-21 14:37 UTCCISA KEV update
  20. 2026-07-21 11:06 UTCVendor advisory
  21. 2026-07-21 11:06 UTCGHSA enrichment
  22. 2026-07-21 07:01 UTCVendor advisory
  23. 2026-07-21 07:00 UTCGHSA enrichment
  24. 2026-07-21 02:58 UTCVendor advisory
  25. 2026-07-21 02:58 UTCGHSA enrichment
Show 75 more
  1. 2026-07-20 22:54 UTCVendor advisory
  2. 2026-07-20 22:54 UTCGHSA enrichment
  3. 2026-07-20 18:51 UTCVendor advisory
  4. 2026-07-20 18:51 UTCGHSA enrichment
  5. 2026-07-20 14:48 UTCVendor advisory
  6. 2026-07-20 14:48 UTCGHSA enrichment
  7. 2026-07-20 10:45 UTCGHSA enrichment
  8. 2026-07-20 06:43 UTCVendor advisory
  9. 2026-07-20 06:42 UTCGHSA enrichment
  10. 2026-07-20 02:01 UTCVendor advisory
  11. 2026-07-20 02:01 UTCGHSA enrichment
  12. 2026-07-19 21:58 UTCVendor advisory
  13. 2026-07-19 21:58 UTCGHSA enrichment
  14. 2026-07-19 17:55 UTCVendor advisory
  15. 2026-07-19 17:55 UTCGHSA enrichment
  16. 2026-07-19 13:52 UTCVendor advisory
  17. 2026-07-19 13:52 UTCGHSA enrichment
  18. 2026-07-19 09:49 UTCVendor advisory
  19. 2026-07-19 09:49 UTCGHSA enrichment
  20. 2026-07-19 05:46 UTCVendor advisory
  21. 2026-07-19 05:46 UTCGHSA enrichment
  22. 2026-07-19 01:42 UTCGHSA enrichment
  23. 2026-07-18 21:38 UTCVendor advisory
  24. 2026-07-18 21:38 UTCGHSA enrichment
  25. 2026-07-18 17:35 UTCVendor advisory
  26. 2026-07-18 17:35 UTCGHSA enrichment
  27. 2026-07-18 13:32 UTCVendor advisory
  28. 2026-07-18 13:32 UTCGHSA enrichment
  29. 2026-07-18 09:28 UTCVendor advisory
  30. 2026-07-18 09:28 UTCGHSA enrichment
  31. 2026-07-18 05:25 UTCVendor advisory
  32. 2026-07-18 05:25 UTCGHSA enrichment
  33. 2026-07-18 01:22 UTCVendor advisory
  34. 2026-07-18 01:22 UTCGHSA enrichment
  35. 2026-07-17 21:19 UTCVendor advisory
  36. 2026-07-17 21:19 UTCGHSA enrichment
  37. 2026-07-17 17:16 UTCVendor advisory
  38. 2026-07-17 17:16 UTCGHSA enrichment
  39. 2026-07-17 13:13 UTCVendor advisory
  40. 2026-07-17 13:13 UTCGHSA enrichment
  41. 2026-07-17 09:10 UTCEG score recompute
  42. 2026-07-17 09:10 UTCVendor advisory
  43. 2026-07-17 09:10 UTCGHSA enrichment
  44. 2026-07-17 05:06 UTCVendor advisory
  45. 2026-07-17 05:06 UTCGHSA enrichment
  46. 2026-07-17 01:02 UTCVendor advisory
  47. 2026-07-17 01:02 UTCGHSA enrichment
  48. 2026-07-16 21:00 UTCVendor advisory
  49. 2026-07-16 21:00 UTCGHSA enrichment
  50. 2026-07-16 17:04 UTCCISA KEV update
  51. 2026-07-16 16:57 UTCVendor advisory
  52. 2026-07-16 16:57 UTCGHSA enrichment
  53. 2026-07-16 12:53 UTCVendor advisory
  54. 2026-07-16 12:53 UTCGHSA enrichment
  55. 2026-07-16 08:50 UTCVendor advisory
  56. 2026-07-16 08:50 UTCGHSA enrichment
  57. 2026-07-16 04:47 UTCVendor advisory
  58. 2026-07-16 04:47 UTCGHSA enrichment
  59. 2026-07-16 00:44 UTCVendor advisory
  60. 2026-07-16 00:44 UTCGHSA enrichment
  61. 2026-07-15 20:41 UTCVendor advisory
  62. 2026-07-15 20:41 UTCGHSA enrichment
  63. 2026-07-15 16:49 UTCCISA KEV update
  64. 2026-07-15 16:38 UTCVendor advisory
  65. 2026-07-15 16:37 UTCGHSA enrichment
  66. 2026-07-15 15:04 UTCCISA KEV update
  67. 2026-07-15 12:34 UTCVendor advisory
  68. 2026-07-15 12:34 UTCGHSA enrichment
  69. 2026-07-15 08:30 UTCVendor advisory
  70. 2026-07-15 08:30 UTCGHSA enrichment
  71. 2026-07-15 04:27 UTCVendor advisory
  72. 2026-07-15 04:26 UTCGHSA enrichment
  73. 2026-07-15 00:22 UTCVendor advisory
  74. 2026-07-15 00:22 UTCGHSA enrichment
  75. 2026-07-14 20:19 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-23397
    First 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 ↗
  • GitHub PoCMuhammad-Ali007/OutlookNTLM_CVE-2023-23397
    First seen Jul 14, 2023
    Open source ↗
  • GitHub PoCvlad-a-man/CVE-2023-23397
    First seen May 7, 2023

    CVE-2023-23397 PoC

    Open source ↗
  • GitHub PoCBronzeBee/cve-2023-23397
    First seen Mar 22, 2023

    Python script for sending e-mails with CVE-2023-23397 payload using SMTP

    Open source ↗
  • GitHub PoCtiepologian/CVE-2023-23397
    First seen Mar 21, 2023

    Proof of Concept for CVE-2023-23397 in Python

    Open source ↗
  • GitHub PoCTrackflaw/CVE-2023-23397
    First seen Mar 20, 2023

    Simple PoC of the CVE-2023-23397 vulnerability with the payload sent by email.

    Open source ↗
  • GitHub PoCdjackreuter/CVE-2023-23397-PoC
    First seen Mar 18, 2023
    Open source ↗
  • GitHub PoCBillSkiCO/CVE-2023-23397_EXPLOIT
    First seen Mar 17, 2023

    Generates meeting requests taking advantage of CVE-2023-23397. This requires the outlook thick client to send.

    Open source ↗
  • GitHub PoCapi0cradle/CVE-2023-23397-POC-Powershell
    First seen Mar 16, 2023
    Open source ↗
  • GitHub PoCka7ana/CVE-2023-23397
    First seen Mar 16, 2023

    Simple PoC in PowerShell for CVE-2023-23397

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(6)

What is CVE-2023-23397?
CVE-2023-23397 is a critical vulnerability published on March 14, 2023. Microsoft Outlook Elevation of Privilege Vulnerability
When was CVE-2023-23397 disclosed?
CVE-2023-23397 was first published in the National Vulnerability Database on March 14, 2023, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-23397 actively exploited?
Yes. CISA added CVE-2023-23397 to the Known Exploited Vulnerabilities catalog on March 14, 2023, affecting Microsoft Office. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2023-23397?
CVE-2023-23397 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2023-23397?
CVE-2023-23397 affects Microsoft Office. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2023-23397?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-23397, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-23397

Explore →

Is Your Infrastructure Affected by CVE-2023-23397?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs