Threats / Microsoft / CVE-2018-8174
CVE-2018-8174
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Microsoft Windows vulnerability
A remote code execution vulnerability in the Windows VBScript engine allows attackers to execute arbitrary code by manipulating objects in memory. The flaw has been actively exploited in ransomware campaigns.
Verdict
Today item, not a backlog item.
Critical vulnerability enabling unauthenticated remote code execution through VBScript object handling. High exploitation prevalence in ransomware operations demonstrates significant real-world threat. Immediate patching required for all affected Windows systems.
CISA KEV Yes · 2022-02-153Ransomware use Flagged3EPSS 0.87814 (verify live)4Exploit Weaponized · public PoC5
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
28 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-02-15), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.87814 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-787 Out-of-bounds Write — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious VBScript or document that exploits improper object memory handling to trigger code execution.
Business
Attackers gain arbitrary code execution capability on target systems without authentication.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I deliver the exploit through email, web, or other vectors to compromise user endpoints.
Business
Initial compromise establishes foothold for lateral movement and persistence across the network.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute ransomware payloads or establish command and control access on compromised machines.
Business
Ransomware deployment encrypts critical data and systems, halting business operations and triggering extortion demands.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05