CVE-2019-16057

CRITICALNVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-04-15), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 4 sources updated this weekExploited in the wild
9.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 87%CVSS: 9.8Exploit: NoneExposed: 0

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

The login_mgr.cgi script in D-Link DNS-320 through 2.05.B10 is vulnerable to remote command injection.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
99(Act)
EG Risk 99/100SSVC: Act

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
Severity98% × 45%
Exploitation100% × 40%
Automatability100% × 15%
Action: Fix now — active exploitation, automatable, high impact.
EPSS
99.7%
KEV
⚠ Exploited

Published

September 16, 2019

Last Modified

November 6, 2025

Advisory Details (2)

Auto-updated May 26, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: cisa.
cisa Patch Available🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-16057
generic🟡 PoC Available

CyStack | Security Research

https://blog.cystack.net/d-link-dns-320-rce/

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 47× in last 7d / 218× 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 401 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

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

  • Nucleihttp/cves/2019/CVE-2019-16057.yaml
    First seen Jan 1, 2019

    D-Link DNS-320 - Remote Code Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2019-16057?
CVE-2019-16057 is a critical vulnerability published on September 16, 2019. The login_mgr.cgi script in D-Link DNS-320 through 2.05.B10 is vulnerable to remote command injection.
When was CVE-2019-16057 disclosed?
CVE-2019-16057 was first published in the National Vulnerability Database on September 16, 2019, with the most recent update on November 6, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-16057 actively exploited?
Yes. CISA added CVE-2019-16057 to the Known Exploited Vulnerabilities catalog on April 15, 2022, affecting D-Link DNS-320 Storage Device. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2019-16057?
CVE-2019-16057 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2019-16057?
CVE-2019-16057 affects D-Link DNS-320 Storage Device. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2019-16057?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-16057, 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-2019-16057

Explore →

Is Your Infrastructure Affected by CVE-2019-16057?

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

Start Free Scan →Browse All CVEs