Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-23399 is a high-severity Out-of-bounds Read (CWE-125) vulnerability in Microsoft Office. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked in the top 15% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Microsoft Excel contains a remote code execution vulnerability tracked as CVE-2023-23399. The flaw is rated 7.8 under CVSS 3.1 with an attack vector that is local, requires low complexity and no privileges, but does need user interaction; successful exploitation can result in full compromise of confidentiality, integrity, and availability. The issue is also associated with CWE-125.
An attacker can exploit the vulnerability by supplying a specially crafted Excel file that the victim must open locally. Because no authentication is required beyond that interaction, an adversary who convinces a target to open the document can execute arbitrary code with the privileges of the current user.
Microsoft has published official guidance and patches for the vulnerability through its Security Response Center update guide at the referenced URL. The EPSS score has remained flat at 0.0735 with no material increase since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-27499
Vulnerability Data
Microsoft Excel Remote Code Execution Vulnerability
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Vulnerability scanning and recording can discover instances of out-of-bounds reads after code is deployed.
Routine patching replaces vulnerable code containing out-of-bounds read flaws.
Secure-development practices such as bounds checking and memory-safe languages directly prevent out-of-bounds reads.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.