Skip to content
Fencer Intel
medium 5.5

CVE-2013-3896 kev in the critical feed json

Microsoft Silverlight 5 before 5.1.20913.0 does not properly validate pointers during access to Silverlight elements, which allows remote a…

published 13y ago modified 4mo ago also EUVD-2013-3828

cvss
5.5
version 3.1, CNA
cisa kev
Exploited
added 2022-05-25
epss
67.1%
EPSS 67.1% chance of exploitation in 30 days, percentile 99.3%
public exploits
2
Metasploit and Exploit-DB

Summary

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."

Patch / fix

cisa required action The impacted product is end-of-life and should be disconnected if still in use.

  • microsoft silverlight 5.1.20913.0

Is CVE-2013-3896 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit exploit/windows/browser/ms13_022_silverlight_script_object)
  2. Published
  3. Added to CISA KEV
  4. CISA patch deadline
  5. CISA SSVC: exploitation active

Known exploited

Added
4y ago
Patch by
2022-06-15 (4y ago)
Ransomware
Not known
Required action
The impacted product is end-of-life and should be disconnected if still in use.
Vendor, product
Microsoft, Silverlight
CISA name
Microsoft Silverlight Information Disclosure Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

67.14% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
CISA ADP 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.