Home › Intelligence › Brief
VULNERABILITY BRIEF🟠 High Vulnerability

Remote Code Execution in Microsoft Office and WordPad (CVE-2017-0199) Threatens Enterprise Documents

A remote code execution vulnerability (CVE-2017-0199) in Microsoft Office and WordPad allows attackers to execute arbitrary code when a crafted file is opened. The flaw underscores the need for robust patch management and evidence of remediation to satisfy audit requirements.

LiveThreat™ Intelligence · 📅 October 07, 2026· 📰 nvd.nist.gov
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
2 sector(s)
✅
Actions
4 recommended
📰
Source
nvd.nist.gov

Remote Code Execution in Microsoft Office and WordPad (CVE-2017-0199) Threatens Enterprise Documents

What It Is — A remote‑code‑execution flaw (CVE‑2017‑0199) exists in Microsoft Office and WordPad’s file‑parsing logic. An attacker who convinces a user to open a specially crafted document can execute arbitrary code on the victim’s machine.

Exploitability — Publicly disclosed; proof‑of‑concept code is available. No known active exploit campaign at the time of writing, but the vulnerability is trivial to weaponize once a malicious file is delivered. CVSS v3.1 base score 7.8 (High).

Affected Products — Microsoft Office (all supported versions) and Windows WordPad.

Why It Matters for Trust & Control Assurance

  • Patch Management / Vulnerability Remediation – Demonstrates the need for a documented, repeatable process that tracks patch deployment and provides auditable evidence of remediation.
  • Continuous Monitoring – Real‑time scanning for the vulnerable file types and verification that patches are applied feeds into a defensible control‑assurance audit trail.
  • Supply‑Chain Assurance – Office files are a common attack vector; proving timely updates strengthens the organization’s overall trust posture with partners and regulators.

Recommended Actions

  • Inventory all endpoints running the affected Office/WordPad versions.
  • Deploy Microsoft’s security update for CVE‑2017‑0199 immediately.
  • Record patch status in your configuration‑management database (CMDB) or control‑evidence repository.
  • Integrate the patch‑lifecycle into your continuous control‑monitoring platform to generate ready‑to‑audit evidence.

Source: CISA KEV – CVE‑2017‑0199

📰 Original Source
https://nvd.nist.gov/vuln/detail/CVE-2017-0199 ↗

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Trust Operations

Misconfigurations are control gaps in disguise.

Verisq AI Trust Operations turns findings like this into mapped controls with continuous evidence, keeping your audit readiness current instead of point-in-time.

Map your controls with Verisq AI Trust Operations →