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. 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.
This vulnerability carries a HIGH severity rating with a CVSS v3.1 score of 7.8, requiring local system access to exploit with relatively low complexity though user interaction is required and does not require pre-existing privileges . The vulnerability impacts confidentiality (data exposure), integrity (unauthorized modifications), and availability (service disruption) for affected systems. Impacting 7 products from microsoft, from microsoft, from microsoft and 4 others, organizations running these solutions should prioritize assessment and patching.
First disclosed in 2019, this vulnerability was reported during a period defined by widespread IoT adoption challenges, mobile security concerns, and the emergence of advanced persistent threat (APT) techniques. Contemporary mitigation strategies focused on secure development practices and third-party component vetting.
2019-06-12T14:29:03.557
2025-05-20T18:15:38.893
Modified
CVSSv3.0: 7.8 (HIGH)
AV:N/AC:M/Au:N/C:C/I:C/A:C
8.6
10.0
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | microsoft | office | 2010 | Yes |
| Application | microsoft | office | 2016 | Yes |
| Application | microsoft | office | 2019 | Yes |
| Application | microsoft | office | 2019 | Yes |
| Application | microsoft | office_365_proplus | - | Yes |
| Application | microsoft | office_online_server | - | Yes |
| Application | microsoft | office_web_apps | 2010 | Yes |
| Application | microsoft | sharepoint_enterprise_server | 2013 | Yes |
| Application | microsoft | sharepoint_enterprise_server | 2016 | Yes |
| Application | microsoft | sharepoint_server | 2010 | Yes |
| Application | microsoft | sharepoint_server | 2019 | Yes |
| Application | microsoft | word | 2010 | Yes |
| Application | microsoft | word | 2013 | Yes |
| Application | microsoft | word | 2013 | Yes |
| Application | microsoft | word | 2016 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For microsoft's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.