Skip to content
Fencer Vulns
medium 5.5

CVE-2020-1503 json

Microsoft Word Information Disclosure Vulnerability

published 2020-08-17 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-12377

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.6%
EPSS 4.6% chance of exploitation in 30 days, percentile 91%
public exploits
0
none known

Summary

An information disclosure vulnerability exists when Microsoft Word 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 Word functions handle objects in memory.

Patch / fix

Exploit prediction

4.55% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N

Affected products

  • Microsoft Microsoft SharePoint Enterprise Server 2016
  • Microsoft Microsoft SharePoint Enterprise Server 2013 Service Pack 1
  • Microsoft Microsoft SharePoint Server 2019
  • Microsoft Microsoft Office 2019
  • Microsoft Microsoft Office 2019 for Mac
  • Microsoft Microsoft Office Online Server
  • Microsoft Microsoft 365 Apps for Enterprise
  • Microsoft Microsoft Word 2016
  • Microsoft Microsoft Office 2016 for Mac
  • Microsoft Microsoft Office 2010 Service Pack 2
  • Microsoft Microsoft Office Web Apps 2010 Service Pack 2
  • Microsoft Microsoft Office Web Apps 2013 Service Pack 1
  • Microsoft Microsoft SharePoint Server 2010 Service Pack 2
  • Microsoft Microsoft Word 2010 Service Pack 2
  • Microsoft Microsoft Word 2013 Service Pack 1

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.