CVE-2013-1603

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 64.3%, top 2% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Weaponized
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 16%CVSS: 5.3Exploit: NoneExposed: 0

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

An Authentication vulnerability exists in D-LINK WCS-1100 1.02, TESCO DCS-2121 1.05_TESCO, TESCO DCS-2102 1.05_TESCO, DCS-7510 1.00, DCS-7410 1.00, DCS-6410 1.00, DCS-5635 1.01, DCS-5605 1.01, DCS-5230L 1.02, DCS-5230 1.02, DCS-3430 1.02, DCS-3411 1.02, DCS-3410 1.02, DCS-2121 1.06_FR, DCS-2121 1.06, DCS-2121 1.05_RU, DCS-2102 1.06_FR, DCS-2102 1.06, DCS-2102 1.05_RU, DCS-1130L 1.04, DCS-1130 1.04_US, DCS-1130 1.03, DCS-1100L 1.04, DCS-1100 1.04_US, and DCS-1100 1.03 due to hard-coded credentials that serve as a backdoor, which allows remote attackers to access the RTSP video stream.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
96.5%
KEV
Not listed

Published

January 28, 2020

Last Modified

November 21, 2024

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 27× 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-11 08:23 UTCEPSS rescore
  2. 2026-07-09 19:05 UTCEPSS rescore
  3. 2026-07-08 15:10 UTCEPSS rescore
  4. 2026-07-05 02:26 UTCEPSS rescore
  5. 2026-07-01 15:02 UTCEPSS rescore
  6. 2026-06-30 23:19 UTCEPSS rescore
  7. 2026-06-30 23:19 UTCEPSS rescore
  8. 2026-06-29 14:02 UTCEPSS rescore
  9. 2026-06-28 14:03 UTCEPSS rescore
  10. 2026-06-28 04:53 UTCEPSS rescore
  11. 2026-06-28 04:53 UTCEPSS rescore
  12. 2026-06-27 03:05 UTCEPSS rescore
  13. 2026-06-25 13:46 UTCEPSS rescore
  14. 2026-06-24 14:02 UTCEPSS rescore
  15. 2026-06-24 14:02 UTCEPSS rescore
  16. 2026-06-23 21:30 UTCEPSS rescore
  17. 2026-06-21 14:53 UTCEPSS rescore
  18. 2026-06-21 01:57 UTCEPSS rescore
  19. 2026-06-21 01:56 UTCEPSS rescore
  20. 2026-06-18 17:49 UTCEPSS rescore
  21. 2026-06-18 17:49 UTCEPSS rescore
  22. 2026-06-17 17:49 UTCEPSS rescore
  23. 2026-06-17 17:49 UTCEPSS rescore
  24. 2026-06-16 17:49 UTCEPSS rescore
  25. 2026-06-16 17:49 UTCEPSS rescore
Show 24 more
  1. 2026-06-15 17:44 UTCEPSS rescore
  2. 2026-06-12 23:08 UTCEPSS rescore
  3. 2026-06-11 13:56 UTCEPSS rescore
  4. 2026-06-10 13:18 UTCEPSS rescore
  5. 2026-06-07 15:22 UTCEPSS rescore
  6. 2026-06-06 13:45 UTCEPSS rescore
  7. 2026-06-06 13:45 UTCEPSS rescore
  8. 2026-06-05 22:44 UTCEPSS rescore
  9. 2026-06-05 22:44 UTCEPSS rescore
  10. 2026-06-05 06:08 UTCEPSS rescore
  11. 2026-06-05 06:08 UTCEPSS rescore
  12. 2026-06-02 20:10 UTCEPSS rescore
  13. 2026-06-02 20:10 UTCEPSS rescore
  14. 2026-06-01 13:49 UTCEPSS rescore
  15. 2026-06-01 13:49 UTCEPSS rescore
  16. 2026-05-29 13:41 UTCEPSS rescore
  17. 2026-05-29 13:41 UTCEPSS rescore
  18. 2026-05-27 13:38 UTCEPSS rescore
  19. 2026-05-27 13:38 UTCEPSS rescore
  20. 2026-05-27 08:29 UTCEG score recompute
  21. 2026-05-27 08:29 UTCGHSA enrichment
  22. 2026-05-26 07:16 UTCEPSS rescore
  23. 2026-05-26 07:16 UTCEPSS rescore
  24. 2026-05-24 16:43 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-25138✓ verified
    First seen May 1, 2013

    D-Link IP Cameras - Multiple Vulnerabilities

    Open source ↗

Frequently asked(5)

What is CVE-2013-1603?
CVE-2013-1603 is a medium vulnerability published on January 28, 2020. An Authentication vulnerability exists in D-LINK WCS-1100 1.02, TESCO DCS-2121 1.05TESCO, TESCO DCS-2102 1.05TESCO, DCS-7510 1.00, DCS-7410 1.00, DCS-6410 1.00, DCS-5635 1.01, DCS-5605 1.01, DCS-5230L 1.02, DCS-5230 1.02, DCS-3430 1.02, DCS-3411 1.02, DCS-3410 1.02, DCS-2121 1.06FR, DCS-2121 1.06,…
When was CVE-2013-1603 disclosed?
CVE-2013-1603 was first published in the National Vulnerability Database on January 28, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-1603 actively exploited?
CVE-2013-1603 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2013-1603?
CVE-2013-1603 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2013-1603?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-1603, 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-1603

Explore →

Is Your Infrastructure Affected by CVE-2013-1603?

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