How severe is CVE-2013-3896?

CVE-2013-3896 has a CVSS score of 5.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2013-3896?

Affected package information for CVE-2013-3896 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2013-3896?

No fixed release is recorded for CVE-2013-3896 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2013-3896 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2013-3896 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2013-3896 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2013-3896, including 1 documented proof-of-concept exploit on Exploit-DB and 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2013-3896?

CVE-2013-3896 has an EPSS (Exploit Prediction Scoring System) score of 68.0%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2013-3896 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2013-3896 (Microsoft Silverlight Information Disclosure Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-05-25. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-06-15. The required action was: The impacted product is end-of-life and should be disconnected if still in use. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

When was CVE-2013-3896 published, and has it been updated?

CVE-2013-3896 was published on October 9, 2013 and was last updated on October 22, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

MEDIUM severity

CVE-2013-3896 — Microsoft

MEDIUM

CVE-2013-3896 is a medium-severity (CVSS 5.5) vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-05-25) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

Microsoft Silverlight 5 before 5.1.20913.0 does not properly validate pointers during access to Silverlight elements, which allows remote attackers to obtain sensitive information via…

Published

Oct 9, 2013

Updated

Oct 22, 2025

Affected

1 product

Patched

See advisory

Exploits

4 known

Exploitation data as of Oct 20, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-05-25. Federal agencies were required to remediate by 2022-06-15.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2013-3896.

EPSS Exploitation Probability

via FIRST.org ↗

68.0%probability of exploitation in next 30 days

High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2013-3896 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Counts from FIRST.org, log-scaled.

Description

Microsoft Silverlight 5 before 5.1.20913.0 does not properly validate pointers during access to Silverlight elements, which allows remote attackers to obtain sensitive information via a crafted Silverlight application, aka "Silverlight Vulnerability."

Affected Products

1 product · 1 configurations

Application

silverlightmicrosoft

≥ 5.0 && < 5.1.20913.0

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-41702localwindows✓ Verified

Microsoft Silverlight - ScriptObject Unsafe Memory Access (MS13-022/MS13-087) (Metasploit)

by Metasploit · Mar 12, 2013

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2013-3896 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-3896 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works