vciy

CVE-2020-1497

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 Excel Information Disclosure Vulnerability

CVE-2020-14974 of 4 sources documented this
23

rank 23 = 1 + 14 + 1 + 7 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.04639  ·  without this subject the record ranks 22

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.5, from NVD  ·  without this subject the record ranks 9

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2025-07-08  ·  without this subject the record ranks 22

How much of the world it touches

NVD CPE configurations

7 products in the CPE ranges  ·  without this subject the record ranks 16

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$142,000over the next 30 days, if this record is yours
Movement+$83,800on 2025-03-25, the last material move, 1 year, 2 months before this reading
Basisassumeda published average, not your estate

$142,000 = $4.99M incident cost x 0.6121449559255632 exposure x 0.04639 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.04639EPSSNOT IN KEVas of 2026-09-20
Severity5.5 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementthreshold crossedreceipt
STEADY10Holding near 0.05 across 37 observations. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

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 lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classNo CWE mapping in held sources.

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed inNo fix version in held sources, as the index stood on 15 Jun 2026.
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, NVD5.5 MEDIUMreceipt
Exploit probability0.04639 · top 9% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes37 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Office 2019; Microsoft 365 Apps for Enterprise; Microsoft Excel 2016; Microsoft Office 2016; Microsoft Excel 2010 Service Pack 2; Microsoft Excel 2013 Service Pack 1…receipt
Published rangesmicrosoft excel 2010; microsoft excel 2013; microsoft excel 2016; microsoft office 2010receipt
Show all 7 published ranges
microsoft excel 2010
microsoft excel 2013
microsoft excel 2016
microsoft office 2010
microsoft office 2013
microsoft office 2016
microsoft office 2019

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.

What it is stated by the CNA

An information disclosure vulnerability exists when Microsoft Excel improperly discloses the contents of its memory. An attacker who exploited the vulnerability could use the information to compromise the user’s computer or data. To exploit the vulnerability, an attacker could craft a special document file and then convince the user to open it. An attacker must know the memory address location where the object was created. The update addresses the vulnerability by changing the way certain Excel functions handle objects in memory. receipt

NVD's analysis a second authority

severity
5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
affected versions
microsoft excel 2010; microsoft excel 2013; microsoft excel 2016; and 4 more, listed in full below

check it yourself portal.msrc.microsoft.com receipt

Dated events

2022-01-06EPSS moved 0.05 to 0.182026-06-15EPSS moved 0.28 to 0.05

Movement the material steps

14 Apr 20210.04557
6 Jan 20220.17642 · crossed 0.10
1 Apr 20220.02632 · crossed 0.10
7 Mar 20230.00116 · scoring model v2023.03.01
17 Mar 20250.10117 · crossed 0.10 · scoring model v2025.03.14
19 Mar 20250.0894 · crossed 0.10
25 Mar 20250.11684 · crossed 0.10
12 Jun 20250.22267
15 Jun 20260.04639 · crossed 0.10 · scoring model v2026.06.15
Show all 37 observations
14 Apr 20210.04557
6 Jan 20220.17642
4 Feb 20220.16892
5 Mar 20220.18093
1 Apr 20220.02632
7 Mar 20230.00116
12 Mar 20230.00104
24 Mar 20230.00106
20 Apr 20230.00104
3 May 20230.00148
10 Jul 20230.01211
24 Jul 20230.00990
21 Aug 20230.00857
4 Sep 20230.01668
21 Dec 20230.01362
21 Jan 20240.01587
14 Mar 20240.01352
8 Jul 20240.00758
10 Sep 20240.00957
12 Oct 20240.00734
27 Oct 20240.00662
12 Nov 20240.00339
11 Dec 20240.00312
17 Dec 20240.00442
29 Dec 20240.00451
13 Jan 20250.00442
17 Mar 20250.10117
19 Mar 20250.0894
25 Mar 20250.11684
29 Mar 20250.1973
30 Mar 20250.11684
17 May 20250.19194
11 Jun 20250.19323
12 Jun 20250.22267
8 Jul 20250.25763
17 Dec 20250.28459
15 Jun 20260.04639

37 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.04639Published2020-08-17Index as of2026-06-15

The record had been public for 5 years, 9 months when this index was last written.

Published 2020-08-17 receipt · Index as of 2026-06-15 derived

Siblings and hubs

Records related to this one

Its defect family

microsoft office

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

Nothing we hold separates this record from the others in its defect family. 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-2020-1497.

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.