vciy

CVE-2019-1035

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-2019-10354 of 4 sources documented this
27

rank 27 = 2 + 20 + 0 + 5 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.06558  ·  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 NVD  ·  without this subject the record ranks 7

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 27

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$327,000over the next 30 days, if this record is yours
Movement+$164,000on 2025-11-03, the last material move, 7 months before this reading
Basisassumeda published average, not your estate

$327,000 = $4.99M incident cost x 1 exposure x 0.06558 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.06558EPSSNOT IN KEVas of 2026-09-20
Severity7.8 HIGHreceipt
Harmtotal lossreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementthreshold crossedreceipt
PLATEAU10Minimal movement since 2025-05-21, 390 days at 0.07, as of 2026-06-15. 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 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 · 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, NVD7.8 HIGHreceipt
Exploit probability0.06558 · top 6% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes47 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft SharePoint Server 2019; Microsoft Office 2019; Microsoft Office 2019 for Mac; Microsoft Office 365 ProPlus; Microsoft Office Online Server; 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

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. To exploit the vulnerability, a user must open a specially crafted file with an affected version of Microsoft Word software. 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. receipt

Read the rest of the CNA's description

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. The security update addresses the vulnerability by correcting how Microsoft Word handles files in memory.

NVD's analysis a second authority

severity
7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
affected versions
microsoft office 2016; microsoft office 2019; microsoft sharepoint server 2019

check it yourself msrc.microsoft.com receipt

Dated events

2022-01-06EPSS moved 0.14 to 0.422026-06-15EPSS moved 0.12 to 0.07

Movement the material steps

14 Apr 20210.13741
6 Jan 20220.41682
1 Apr 20220.05242 · crossed 0.10
7 Mar 20230.00883 · scoring model v2023.03.01
17 Mar 20250.2629 · crossed 0.10 · scoring model v2025.03.14
19 Mar 20250.36319
29 Mar 20250.60059 · crossed 0.50
30 Mar 20250.36319 · crossed 0.50
21 May 20250.09767 · crossed 0.10
11 Jun 20250.13047 · crossed 0.10
24 Oct 20250.09767 · crossed 0.10
3 Nov 20250.13047 · crossed 0.10
15 Jun 20260.06558 · crossed 0.10 · scoring model v2026.06.15
Show all 47 observations
14 Apr 20210.13741
6 Jan 20220.41682
4 Feb 20220.32708
1 Apr 20220.05242
21 May 20220.05698
7 Dec 20220.07289
7 Mar 20230.00883
14 Mar 20230.01462
25 Mar 20230.02474
1 Apr 20230.01387
16 Apr 20230.05849
3 May 20230.01542
19 May 20230.01581
5 Jun 20230.02001
19 Jun 20230.01421
7 Aug 20230.02075
22 Aug 20230.01267
21 Sep 20230.01674
24 Oct 20230.02355
8 Nov 20230.02468
23 Nov 20230.02006
24 Dec 20230.02110
6 Jan 20240.01761
26 Jan 20240.01787
7 Feb 20240.01751
27 Feb 20240.02463
12 Mar 20240.02204
23 Jun 20240.01763
3 Sep 20240.01405
20 Sep 20240.01531
2 Nov 20240.01732
23 Nov 20240.01666
17 Dec 20240.00907
17 Mar 20250.2629
19 Mar 20250.36319
29 Mar 20250.60059
30 Mar 20250.36319
18 May 20250.30269
21 May 20250.09767
11 Jun 20250.13047
24 Oct 20250.09767
3 Nov 20250.13047
18 Nov 20250.10481
21 Nov 20250.13047
28 Mar 20260.12836
13 May 20260.12424
15 Jun 20260.06558

47 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.06558Published2019-06-12Index as of2026-06-15

The record had been public for 7 years when this index was last written.

Published 2019-06-12 receipt · Index as of 2026-06-15 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-2019-1035.

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.