vciy

CVE-2020-1338

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 Word Remote Code Execution Vulnerability

CVE-2020-13384 of 4 sources documented this
23

rank 23 = 1 + 17 + 0 + 5 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.03851  ·  without this subject the record ranks 22

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 6.8, from NVD  ·  without this subject the record ranks 6

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 23

How much of the world it touches

NVD CPE configurations

3 products in the CPE ranges  ·  without this subject the record ranks 18

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$192,000over the next 30 days, if this record is yours
Movement+$68,000on 2025-11-21, the last material move, 9 months before this reading
Basisassumeda published average, not your estate

$192,000 = $4.99M incident cost x 1 exposure x 0.03851 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.03851EPSSNOT IN KEVas of 2026-09-20
Severity7.8 HIGHreceipt
Harmtotal lossreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementfallenreceipt
PLATEAU10Minimal movement since 2023-08-04, 1122 days at 0.04, as of 2026-08-30. 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

Sources disagree here.

Severity score
Microsoft7.8 HIGHreceipt
NVD6.8 MEDIUMreceipt
Scoring standard
MicrosoftCVSS v3.1receipt
NVDCVSS v2.0receipt

Both shown, dated. We don't pick winners. disagreement-rules@v1

Running Microsoft SharePoint Server 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 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 30 Aug 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, the CNA7.8 HIGHreceipt
CVSS, NVD6.8 MEDIUMreceipt
Exploit probability0.03851 · top 10% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes50 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft SharePoint Server 2019; Microsoft Office 2019; Microsoft Office 2019 for Mac; Microsoft Office Online Server; Microsoft 365 Apps for Enterprise; Microsoft Office 2016 for Macreceipt
Published rangesmicrosoft office 2016; microsoft office 2019; microsoft sharepoint server 2019receipt

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

<p>A remote code execution vulnerability exists in Microsoft Word software when it fails to properly handle objects in memory. An attacker who successfully exploited the vulnerability could use a specially crafted file to perform actions in the security context of the current user. For example, the file could then take actions on behalf of the logged-on user with the same permissions as the current user.</p> <p>To exploit the vulnerability, a user must open a specially crafted file with an affected version of Microsoft Word software. receipt

Read the rest of the CNA's description

In an email attack scenario, an attacker could exploit the vulnerability by sending the specially crafted file to the user and convincing the user to open the file. In a web-based attack scenario, an attacker could host a website (or leverage a compromised website that accepts or hosts user-provided content) that contains a specially crafted file that is designed to exploit the vulnerability. However, an attacker would have no way to force the user to visit the website. Instead, an attacker would have to convince the user to click a link, typically by way of an enticement in an email or Instant Messenger message, and then convince the user to open the specially crafted file.</p> <p>The security update addresses the vulnerability by correcting how Microsoft Word handles files in memory.</p>

NVD's analysis a second authority

severity
6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
affected versions
microsoft office 2016; microsoft office 2019; microsoft sharepoint server 2019
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 · [email protected] 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

The CNA scored it 7.8 and NVD 6.8. Both are shown because both were published; we do not pick one.

check it yourself portal.msrc.microsoft.com receipt

Dated events

2022-01-06EPSS moved 0.10 to 0.322022-04-01EPSS moved 0.38 to 0.022026-06-15EPSS moved 0.11 to 0.04

Movement the material steps

14 Apr 20210.09575
6 Jan 20220.32208 · crossed 0.10
1 Apr 20220.01875 · crossed 0.10
7 Mar 20230.15645 · crossed 0.10 · scoring model v2023.03.01
4 Aug 20230.08015 · crossed 0.10
17 Mar 20250.02643 · scoring model v2025.03.14
2 Aug 20250.10314 · crossed 0.10
18 Nov 20250.09313 · crossed 0.10
21 Nov 20250.10675 · crossed 0.10
15 Jun 20260.03665 · crossed 0.10 · scoring model v2026.06.15
30 Aug 20260.03851
Show all 50 observations
14 Apr 20210.09575
6 Jan 20220.32208
4 Feb 20220.3577
30 Mar 20220.37706
1 Apr 20220.01875
7 Mar 20230.15645
10 Mar 20230.13946
18 Apr 20230.14756
28 May 20230.17561
23 Jun 20230.10916
21 Jul 20230.14666
4 Aug 20230.08015
18 Aug 20230.08416
15 Oct 20230.09745
29 Oct 20230.07979
29 Nov 20230.08169
29 Dec 20230.08383
1 Jan 20240.07627
15 Jan 20240.05415
30 Jan 20240.04326
15 Feb 20240.03560
3 Mar 20240.04887
21 Mar 20240.03239
8 Apr 20240.04411
25 Apr 20240.03986
11 May 20240.02975
29 May 20240.03130
13 Jun 20240.03524
1 Jul 20240.02954
16 Jul 20240.05337
2 Aug 20240.03173
18 Aug 20240.03252
4 Sep 20240.04091
18 Sep 20240.02928
6 Nov 20240.05454
21 Nov 20240.03391
17 Dec 20240.04821
17 Mar 20250.02643
29 Mar 20250.07823
30 Mar 20250.02643
11 Jun 20250.04741
12 Jun 20250.07867
2 Aug 20250.10314
24 Sep 20250.10594
23 Oct 20250.10675
18 Nov 20250.09313
21 Nov 20250.10675
15 Jun 20260.03665
23 Jul 20260.03635
30 Aug 20260.03851

50 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.03851Published2020-09-11Index as of2026-08-30

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

Published 2020-09-11 receipt · Index as of 2026-08-30 derived

Siblings and hubs

Records related to this one

Its defect family

microsoft sharepoint server

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-1338.

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.