CVE-2011-3625

HIGHCVSS v2 · 9.39.3—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 9.3 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:M/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 24.1% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
9.3EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, public exploit)
CISA-KEV: Not listedEPSS PROB: 24%CVSS v2: 9.3Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · public exploitExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Stack-based buffer overflow in the sub_read_line_sami function in subreader.c in MPlayer, as used in SMPlayer 0.6.9, allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a long string in a SAMI subtitle file.

CVSS v2.0 (legacy)
9.3HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
9.3(low)
EG Risk
72(Track)
EG Risk 72/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity93% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
24%
EPSS %ILE
98%
KEV
Not listed

Published

June 11, 2014

Last Modified

May 6, 2026

References (10)

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
mplayer—2:1.0~rc4.dfsg1+svn33713-2—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
mplayer—2:1.0~rc4.dfsg1+svn33713-2—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
mplayer—2:1.0~rc4.dfsg1+svn33713-2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
mplayer—2:1.0~rc4.dfsg1+svn33713-2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 2× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 104 total refreshes for this CVE.

  1. 2026-08-19 16:58 UTCEPSS rescore
  2. 2026-08-18 13:42 UTCEPSS rescore
  3. 2026-08-15 01:25 UTCEPSS rescore
  4. 2026-08-08 16:31 UTCEPSS rescore
  5. 2026-08-07 12:26 UTCOSV refresh
  6. 2026-08-06 13:41 UTCEPSS rescore
  7. 2026-08-05 19:12 UTCEPSS rescore
  8. 2026-08-04 15:04 UTCEPSS rescore
  9. 2026-08-01 04:10 UTCEPSS rescore
  10. 2026-07-30 01:26 UTCEPSS rescore
  11. 2026-07-26 13:44 UTCEG score recompute▲ 9.30
  12. 2026-07-23 14:14 UTCEPSS rescore
  13. 2026-07-23 01:05 UTCEG score recompute
  14. 2026-07-23 00:09 UTCEG score recompute
  15. 2026-07-22 21:48 UTCEG score recompute
  16. 2026-07-22 14:03 UTCEPSS rescore
  17. 2026-07-22 04:48 UTCOSV refresh
  18. 2026-07-21 15:21 UTCEPSS rescore
  19. 2026-07-20 17:03 UTCEPSS rescore
  20. 2026-07-20 17:03 UTCEPSS rescore
  21. 2026-07-19 02:25 UTCEPSS rescore
  22. 2026-07-19 02:25 UTCEPSS rescore
  23. 2026-07-18 10:00 UTCEPSS rescore
  24. 2026-07-16 16:58 UTCEPSS rescore
  25. 2026-07-15 16:54 UTCEPSS rescore
Show 75 more
  1. 2026-07-15 16:54 UTCEPSS rescore
  2. 2026-07-13 22:25 UTCEPSS rescore
  3. 2026-07-13 06:08 UTCEPSS rescore
  4. 2026-07-11 08:22 UTCEPSS rescore
  5. 2026-07-11 08:22 UTCEPSS rescore
  6. 2026-07-08 15:10 UTCEPSS rescore
  7. 2026-07-08 15:10 UTCEPSS rescore
  8. 2026-07-06 02:19 UTCEPSS rescore
  9. 2026-07-06 02:19 UTCEPSS rescore
  10. 2026-07-05 02:26 UTCEPSS rescore
  11. 2026-07-04 23:56 UTCOSV refresh
  12. 2026-07-04 06:27 UTCEPSS rescore
  13. 2026-07-02 14:01 UTCEPSS rescore
  14. 2026-07-01 15:02 UTCEPSS rescore
  15. 2026-07-01 15:02 UTCEPSS rescore
  16. 2026-06-30 23:19 UTCEPSS rescore
  17. 2026-06-30 23:19 UTCEPSS rescore
  18. 2026-06-29 14:02 UTCEPSS rescore
  19. 2026-06-28 14:03 UTCEPSS rescore
  20. 2026-06-28 04:53 UTCEPSS rescore
  21. 2026-06-28 04:52 UTCEPSS rescore
  22. 2026-06-27 03:05 UTCEPSS rescore
  23. 2026-06-27 03:05 UTCEPSS rescore
  24. 2026-06-25 13:46 UTCEPSS rescore
  25. 2026-06-24 14:02 UTCEPSS rescore
  26. 2026-06-24 14:02 UTCEPSS rescore
  27. 2026-06-23 21:30 UTCEPSS rescore
  28. 2026-06-23 21:30 UTCEPSS rescore
  29. 2026-06-22 14:22 UTCEPSS rescore
  30. 2026-06-22 14:22 UTCEPSS rescore
  31. 2026-06-21 01:56 UTCEPSS rescore
  32. 2026-06-21 01:56 UTCEPSS rescore
  33. 2026-06-19 19:22 UTCEPSS rescore
  34. 2026-06-19 19:22 UTCEPSS rescore
  35. 2026-06-18 17:49 UTCEPSS rescore
  36. 2026-06-18 17:49 UTCEPSS rescore
  37. 2026-06-17 17:49 UTCEPSS rescore
  38. 2026-06-17 17:49 UTCEPSS rescore
  39. 2026-06-17 17:49 UTCEPSS rescore
  40. 2026-06-16 17:49 UTCEPSS rescore
  41. 2026-06-16 11:39 UTCOSV refresh
  42. 2026-06-15 17:44 UTCEPSS rescore
  43. 2026-06-14 23:14 UTCEPSS rescore
  44. 2026-06-14 23:14 UTCEPSS rescore
  45. 2026-06-12 23:08 UTCEPSS rescore
  46. 2026-06-11 13:56 UTCEPSS rescore
  47. 2026-06-10 22:14 UTCEPSS rescore
  48. 2026-06-10 13:17 UTCEPSS rescore
  49. 2026-06-08 14:14 UTCEPSS rescore
  50. 2026-06-08 14:14 UTCEPSS rescore
  51. 2026-06-07 15:22 UTCEPSS rescore
  52. 2026-06-07 15:22 UTCEPSS rescore
  53. 2026-06-06 13:45 UTCEPSS rescore
  54. 2026-06-06 13:44 UTCEPSS rescore
  55. 2026-06-05 22:44 UTCEPSS rescore
  56. 2026-06-05 06:08 UTCEPSS rescore
  57. 2026-06-05 06:07 UTCEPSS rescore
  58. 2026-06-04 13:09 UTCEPSS rescore
  59. 2026-06-04 13:09 UTCEPSS rescore
  60. 2026-06-02 20:10 UTCEPSS rescore
  61. 2026-06-02 20:10 UTCEPSS rescore
  62. 2026-06-01 13:49 UTCEPSS rescore
  63. 2026-06-01 13:49 UTCEPSS rescore
  64. 2026-05-29 13:41 UTCEPSS rescore
  65. 2026-05-29 13:40 UTCEPSS rescore
  66. 2026-05-28 18:28 UTCEG score recompute
  67. 2026-05-28 18:28 UTCGHSA enrichment
  68. 2026-05-27 13:38 UTCEPSS rescore
  69. 2026-05-27 13:38 UTCEPSS rescore
  70. 2026-05-25 14:16 UTCOSV refresh
  71. 2026-05-24 16:43 UTCEPSS rescore
  72. 2026-05-22 21:15 UTCEPSS rescore
  73. 2026-05-22 21:15 UTCEPSS rescore
  74. 2026-05-22 21:15 UTCEPSS rescore
  75. 2026-05-20 22:37 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Metasploit module) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-18954✓ verified
    First seen May 30, 2012

    MPlayer - '.SAMI' Subtitle File Buffer Overflow (Metasploit)

    Open source ↗
  • Metasploitexploit/windows/fileformat/mplayer_sami_bof✓ verified
    First seen May 19, 2011

    MPlayer SAMI Subtitle File Buffer Overflow

    Open source ↗

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2011-3625?
CVE-2011-3625 is a high vulnerability published on June 11, 2014. Stack-based buffer overflow in the subreadline_sami function in subreader.c in MPlayer, as used in SMPlayer 0.6.9, allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a long string in a SAMI subtitle file.
When was CVE-2011-3625 disclosed?
CVE-2011-3625 was first published in the National Vulnerability Database on June 11, 2014, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2011-3625 actively exploited?
CVE-2011-3625 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24% probability of exploitation in the next 30 days, which ranks it in the top 2.3% of all scored CVEs.
How do I remediate CVE-2011-3625?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2011-3625, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2011-3625

Explore →

Is Your Infrastructure Affected by CVE-2011-3625?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs