Threats / Microsoft / CVE-2013-3918
CVE-2013-3918
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft Windows vulnerability
Microsoft Windows InformationCardSigninHelper ActiveX control (icardie.dll) contains an out-of-bounds write vulnerability allowing remote code execution when a user visits a specially crafted webpage.
Verdict
Today item — known-exploited.
An attacker can achieve remote code execution with user-level privileges by hosting a malicious webpage that exploits an out-of-bounds write flaw in the ActiveX control. The vulnerability requires user interaction and affects end-of-life Windows versions.
CISA KEV Yes · 2025-10-064EPSS 0.73872 (verify live)5CVSS 8.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3Exploit Weaponized · public exploit · Metasploit module12
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
5 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 2025-10-06).
Probability (EPSS)
EPSS 0.73872 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) · Affected: Microsoft, Windows. 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.
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 4346 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.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
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 webpage containing malicious content that triggers the out-of-bounds write in the InformationCardSigninHelper ActiveX control.
Business
Attackers gain a reliable vector for distributing malware and establishing persistent access to user systems at scale.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I host the webpage on an attacker-controlled or compromised domain and distribute the link via phishing or watering hole attacks.
Business
Organizations face increased risk of targeted compromise against users who visit untrusted or compromised websites.
3
Lateral reach — past segmentation narrative 3
Attacker
When a user visits the webpage, the vulnerability executes arbitrary code with the privileges of the logged-in user.
Business
Confidential data, intellectual property, and system integrity are compromised within the user's security context.
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