Threats / Microsoft / CVE-2020-0674
CVE-2020-0674
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft Internet Explorer vulnerability
Microsoft Internet Explorer contains a memory corruption vulnerability in the Scripting Engine that could allow remote code execution in the current user's context.
Verdict
Today item — known-exploited.
A use-after-free flaw in Internet Explorer's Scripting Engine enables remote code execution. The high EPSS score and active exploitation in the wild indicate immediate risk to unpatched systems.
CISA KEV Yes · 2021-11-034EPSS 0.86863 (verify live)5Exploit Public PoC6CVSS 7.5 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
10 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 2021-11-03).
Probability (EPSS)
EPSS 0.86863 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.5 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H) · Affected: Microsoft, Internet Explorer. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-416 Use After Free — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 631 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
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 webpage containing specially crafted JavaScript that triggers improper object handling in the Scripting Engine.
Business
Users visiting untrusted or compromised websites face arbitrary code execution with their privileges, risking credential theft and system compromise.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I host the exploit on a website or distribute it via phishing to increase victim reach.
Business
Attack surface expands across web browsing, email, and social engineering vectors, affecting both targeted and opportunistic victims.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute arbitrary code within the user's session to establish persistence or exfiltrate sensitive data.
Business
Confidentiality and integrity of user data are compromised; attackers gain foothold for lateral movement within networks.
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