Skip to content
vulnerability

CVE-2013-3918

8.8
High
KEV · Exploited in wildEPSS 74%Patch available

The InformationCardSigninHelper Class ActiveX control in icardie.dll in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, and Windows RT Gold and 8.1 allows remote attackers to execute arbitrary code or cause a denial of service (out-of-bounds write) via a crafted web page that is accessed by Internet Explorer, as exploited in the wild in November 2013, aka "InformationCardSigninHelper Vulnerability."

exploited
Yes, in CISA KEV since 6 Oct 2025fix by 27 Oct 2025 (CISA deadline for US federal agencies)public exploit code
fix
Patch available see the advisory in the references
likelihood
EPSS 73.7%
Published 12 Nov 2013Analysed here 2 Nov 2026CVSS scored by CISA

do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

triage
server-sideruntimeWAF can block: noAV · networkCWE-787· Out-of-Bounds Write

Can a WAF block it? No. The vulnerability is triggered by visiting a crafted web page in Internet Explorer, but the exploit involves an out-of-bounds write in an ActiveX control, which looks like a normal web request to a WAF and does not contain unusual or filterable input patterns.

Also consider: patch

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexitylowprivileges requirednoneuser interactionrequiredscopeunchangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
common questions

Is CVE-2013-3918 being exploited?

Yes. CVE-2013-3918 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2013-3918?

CVE-2013-3918 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2013-3918?

Yes. A fix has been recorded for CVE-2013-3918. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2013-3918 affect?

CVE-2013-3918 affects microsoft:windows_7, microsoft:windows_8, microsoft:windows_8.1, microsoft:windows_rt, and 6 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
microsoft:windows_7microsoft:windows_8microsoft:windows_8.1microsoft:windows_rtmicrosoft:windows_rt_8.1microsoft:windows_server_2003microsoft:windows_server_2008microsoft:windows_server_2012microsoft:windows_vistamicrosoft:windows_xp

public exploits

Public exploit code: 1 on Exploit-DB · 1 Metasploit module

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
no
technical impact
total

Assessed by CISA 4 Oct 2025 (SSVC 2.0.3).

timeline

  1. 12 Nov 2013Published
  2. 27 Nov 2013First public exploit or proof of concept · 14 days later
  3. 4 Oct 2025CISA SSVC assessment: exploitation active · 4,329 days (about 12 years) later
  4. 6 Oct 2025Added to CISA KEV (exploited in the wild) · 2 days later
  5. 22 Oct 2025CVE record last updated · 16 days later
  6. 27 Oct 2025CISA remediation due date (US federal agencies) · 5 days later
  7. 2 Nov 2026Analysed by vulneraibility.com · 372 days (about 1 year) later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
9 references in the CVE record: 3 advisories, 6 links
  • Advisoryus-cert.gov /ncas/alerts/TA13-317A
  • Advisorydocs.microsoft.com /en-us/security-updates/securitybulletins/2013/ms13-090
  • Advisorymicrosoft.com /en-us/msrc/blog/2013/11/technical-details-of-the-targeted-attack-using-ie-vulne
  • Linkdarkreading.com /vulnerability/new-ie-vulnerability-found-in-the-wild-s/240163814/
  • Linkfireeye.com /blog/technical/2013/11/new-ie-zero-day-found-in-watering-hole-attack.html
  • Linkoval.cisecurity.org /repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A19089
  • Linkisc.sans.edu /forums/diary/16985
  • Linkblogs.technet.com /b/msrc/archive/2013/11/11/activex-control-issue-being-addressed-in-update-tuesd
Show 1 more
  • Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2013-3918

sources

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved