vciy

CVE-2023-21737

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Microsoft Office Visio Remote Code Execution Vulnerability

CVE-2023-217374 of 4 sources documented this
25

rank 25 = 0 + 20 + 0 + 5 + 0

rank@v1 · scheduled

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00723  ·  without this subject the record ranks 25

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.8, from the CNA  ·  without this subject the record ranks 5

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 25

How much of the world it touches

NVD CPE configurations

4 products in the CPE ranges  ·  without this subject the record ranks 20

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 25

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$36,100over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$36,100 = $4.99M incident cost x 1 exposure x 0.00723 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.00723EPSSNOT IN KEVas of 2026-09-20
Severity7.8 HIGHreceipt
Harmtotal lossreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementscoring model changedreceipt
PLATEAU10Minimal movement since 2023-01-11, 1251 days at 0.01, as of 2026-06-15. arc-rules@v1

Foresight · where to check next

Microsoft WindowsMicrosoft WindowsMicrosoft Windows21737

This record is one instance of CWE-122, heap-based buffer overflow. The index holds 3216 prior instances of this class, 20 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Running Microsoft Office 2019? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachneeds local access · no privileges required · user interaction required · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-122 Heap-based Buffer Overflowreceipt
Published consequencesCWE-122: Availability: DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory); Integrity, Confidentiality, Availability, Access Control: Execute…[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in15.0.5519.1000; 16.0.5378.1000receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA7.8 HIGHreceipt
Exploit probability0.00723 · top 47% of all CVEsreceipt
Blast breadth3 products across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes40 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Office 2019; Microsoft 365 Apps for Enterprise; Microsoft Office LTSC 2021; Microsoft Visio 2013 Service Pack 1; Microsoft Visio 2016receipt
Published rangesmicrosoft office 2019; microsoft office long term servicing channel 2021; microsoft visio 2013; microsoft visio 2016receipt
Fixed in15.0.5519.1000; 16.0.5378.1000receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

Attack path

Local accessrequires user interactionMicrosoft Visio 2016CWE-122 weaknessFull compromise (C/I/A)C:H / I:H / A:Hexploits CWE-122data compromise

What it is stated by the CNA

Microsoft Office Visio Remote Code Execution Vulnerability receipt

NVD's analysis a second authority

weakness
CWE-122
affected versions
microsoft office 2019; microsoft office long term servicing channel 2021; microsoft visio 2013; and 1 more, listed in full below
also scored by
[email protected] 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

check it yourself msrc.microsoft.com receipt

Movement the material steps

11 Jan 20230.01103
7 Mar 20230.0011 · scoring model v2023.03.01
17 Mar 20250.00483 · scoring model v2025.03.14
15 Jun 20260.00723 · scoring model v2026.06.15

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 40 observations
11 Jan 20230.01103
19 Jan 20230.01528
7 Mar 20230.0011
8 Mar 20230.00110
14 Apr 20230.00143
19 Apr 20230.00296
27 Apr 20230.00420
28 Apr 20230.00595
8 May 20230.00162
30 Jan 20240.00210
12 Feb 20240.00169
24 Feb 20240.00270
8 Mar 20240.00169
29 Apr 20240.00182
13 May 20240.00199
9 Jun 20240.00250
22 Jun 20240.00275
5 Jul 20240.00254
20 Jul 20240.00261
2 Aug 20240.00339
17 Aug 20240.00383
12 Nov 20240.00362
26 Nov 20240.00335
17 Dec 20240.00530
6 Jan 20250.00628
5 Mar 20250.00568
17 Mar 20250.00483
19 Mar 20250.01173
25 Mar 20250.00939
29 Mar 20250.05026
30 Mar 20250.00939
5 Oct 20250.00987
6 Nov 20250.01053
18 Nov 20250.02667
21 Nov 20250.01053
13 Jan 20260.0116
17 Jan 20260.01279
19 Jan 20260.03217
15 Feb 20260.03285
15 Jun 20260.00723

40 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00723Published2023-01-10Index as of2026-06-15

Exploit probability more than doubled between 2025-03-17 and 2025-03-19 (0.00483 → 0.01173) and the record had been public for 3 years, 5 months when this index was last written.

Published 2023-01-10 receipt · Index as of 2026-06-15 derived

The pattern, elsewhere

This record is one instance of CWE-122, heap-based buffer overflow. The index holds 3216 prior instances of this class, 20 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2025-24985 · Microsoft Windows 10 Version 1507matches 9 of 9KEV listed · 2025receipt
CVE-2025-24993 · Microsoft Windows 10 Version 1507matches 9 of 9KEV listed · 2025receipt
CVE-2024-30051 · Microsoft Windows 10 Version 1809matches 7 of 9KEV listed · 2024receipt
CVE-2023-23376 · Microsoft Windows 10 Version 1507matches 7 of 9KEV listed · 2023receipt
CVE-2023-28252 · Microsoft Windows 10 Version 1809matches 7 of 9KEV listed · 2023receipt
CVE-2026-85880 · Microsoft Windows 10 Version 1607matches 7 of 9KEV listed · 2026receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

3216 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Its defect family

microsoft office 2019

Of the 8 records in this family, this is the only one holding a stated fix version: 15.0.5519.1000; 16.0.5378.1000.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: computed, pro@dim2000

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2023-21737.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.