Skip to content
Fencer Vulns
high 7.8

CVE-2023-23399 json

Microsoft Excel Remote Code Execution Vulnerability

published 2023-03-14 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-27499

cvss
7.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.5%
EPSS 2.5% chance of exploitation in 30 days, percentile 85%
public exploits
1
Exploit-DB

Summary

Microsoft Excel Remote Code Execution Vulnerability

Patch / fix

  • Microsoft Microsoft Office 2019 for Mac 16.71.23031200
  • Microsoft Microsoft Office Online Server 16.0.10396.20000
  • Microsoft Microsoft Office LTSC for Mac 2021 16.71.23031200
  • Microsoft Microsoft Excel 2016 16.0.5387.1000
  • Microsoft Microsoft Office 2016 16.0.5387.1000
  • Microsoft Microsoft Excel 2013 Service Pack 1 15.0.5537.1000
  • Microsoft Microsoft Office 2013 Service Pack 1 15.0.5537.1000
  • Microsoft Microsoft Office Web Apps Server 2013 Service Pack 1 15.0.5537.1000

Timeline

  1. Published
  2. First public exploit (EDB-51328)

Exploit prediction

2.53% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-51328 Microsoft Excel 365 MSO (Version 2302 Build 16.0.16130.20186) 64-bit - Remote Code Execution (RCE) remote, 2023-04-08

CVSS scores

assigned by version score vector
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

  • Microsoft Microsoft Office 2019
  • Microsoft Microsoft Office 2019 for Mac
  • Microsoft Microsoft Office Online Server
  • Microsoft Microsoft 365 Apps for Enterprise
  • Microsoft Microsoft Office LTSC for Mac 2021
  • Microsoft Microsoft Office LTSC 2021
  • Microsoft Microsoft Excel 2016
  • Microsoft Microsoft Office 2016
  • Microsoft Microsoft Excel 2013 Service Pack 1
  • Microsoft Microsoft Office 2013 Service Pack 1
  • Microsoft Microsoft Office Web Apps Server 2013 Service Pack 1

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.