LiveActive security incident?Get immediate response
CVE Record

CVE-2018-8147: A remote code execution vulnerability exists in Microsoft Excel software when the software fails to properl...

A remote code execution vulnerability exists in Microsoft Excel software when the software fails to properly handle objects in memory, aka "Microsoft Excel Remote Code Execution Vulnerability." This affects Microsoft Office, Microsoft Excel. This CVE ID is unique from CVE-2018-8148, CVE-2018-8162.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2018-8147 is a Microsoft Excel remote code execution flaw caused by improper handling of objects in memory. If an affected Office or Excel version processes a malicious file, an attacker may be able to run code on that user’s system. The bundle does not provide CVSS, patch identifiers, or active exploitation evidence. Exposure is most likely on endpoints still running the listed legacy Microsoft Office or Excel versions, especially where users receive and open external spreadsheets or Office documents. Unsupported or poorly inventoried desktop software increases uncertainty. Treat as a high-priority endpoint patching and legacy software cleanup item, not as confirmed emergency exploitation. Focus first on users handling external spreadsheets, finance workflows, and systems running older Office versions. Mitigation focus: Check Microsoft MSRC guidance for CVE-2018-8147 and apply applicable vendor updates.; Inventory affected Office and Excel versions across managed endpoints.; Prioritize remediation for legacy Office 2010, 2013, 2016, Mac 2016, and Compatibility Pack installs..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-8147 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftMicrosoft Office2010 Service Pack 2 (32-bit editions), 2010 Service Pack 2 (64-bit editions), 2013 RT Service Pack 1, 2013 Service Pack 1 (32-bit editions), 2013 Service Pack 1 (64-bit editions), 2016 Click-to-Run (C2R) for 32-bit editions, 2016 Click-to-Run (C2R) for 64-bit editions, 2016 for Mac, Compatibility Pack Service Pack 3Listed
MicrosoftMicrosoft Excel2010 Service Pack 2 (32-bit editions), 2010 Service Pack 2 (64-bit editions), 2013 RT Service Pack 1, 2013 Service Pack 1 (32-bit editions), 2013 Service Pack 1 (64-bit editions), 2016 (32-bit edition), 2016 (64-bit edition)Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.