CVE-2013-3307

HIGHNVD 8.38.3—
EchelonGraph scoreMEDIUM confidence

Score 8.3 from GitHub Security Advisory (severity: HIGH) published 2025-07-11. NVD baseline CVSS 8.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
8.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 6%CVSS: 8.3Exploit: NoneExposed: 0

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

Linksys E1000 devices through 2.1.02, E1200 devices before 2.0.05, and E3200 devices through 1.0.04 allow OS command injection via shell metacharacters in the apply.cgi ping_ip parameter on TCP port 52000.

CVSS v3
8.3
EG Score
8.3(medium)
EG Risk
68(Attend)
EG Risk 68/100SSVC: Attend

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
Severity83% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
92.1%
KEV
Not listed

Published

July 11, 2025

Last Modified

April 15, 2026

References (1)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 36× 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.

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

Publicly available exploits

(1 reference)

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

  • Exploit-DBEDB-26415
    First seen Jun 24, 2013

    Linksys X3000 1.0.03 build 001 - Multiple Vulnerabilities

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2013-3307?
CVE-2013-3307 is a high vulnerability published on July 11, 2025. Linksys E1000 devices through 2.1.02, E1200 devices before 2.0.05, and E3200 devices through 1.0.04 allow OS command injection via shell metacharacters in the apply.cgi ping_ip parameter on TCP port 52000.
When was CVE-2013-3307 disclosed?
CVE-2013-3307 was first published in the National Vulnerability Database on July 11, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-3307 actively exploited?
CVE-2013-3307 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 92.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2013-3307?
CVE-2013-3307 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2013-3307?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-3307, 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

Explore the affected products and dependency analysis for CVE-2013-3307

Explore →

Is Your Infrastructure Affected by CVE-2013-3307?

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

Start Free Scan →Browse All CVEs