Threats / D-Link / CVE-2015-2051
CVE-2015-2051
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
D-Link DIR-645 Router vulnerability
D-Link DIR-645 routers are vulnerable to remote command execution through the HNAP interface, allowing unauthenticated attackers to execute arbitrary commands on affected devices.
Verdict
Today item — known-exploited.
This vulnerability enables direct remote code execution on network infrastructure with high exploitability. The active exploitation in the wild and high EPSS score indicate immediate risk to exposed devices, particularly in environments where routers are internet-facing.
CISA KEV Yes · 2022-02-104EPSS 0.96864 (verify live)5CVSS 8.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3Exploit Weaponized · public exploit · Metasploit module11
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
1034 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-02-10).
Probability (EPSS)
EPSS 0.96864 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.8 (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: D-Link, DIR-645 Router. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-77 Command Injection — weakness family: Injection.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 2544 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify internet-exposed D-Link DIR-645 routers and probe the HNAP interface for the GetDeviceSettings action.
Business
Network perimeter is compromised, establishing a foothold for lateral movement into internal systems.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft a malicious HNAP request to execute arbitrary commands with router privileges.
Business
Router becomes a compromised network node capable of traffic interception, DNS hijacking, and credential harvesting.
3
Lateral reach — past segmentation narrative 3
Attacker
I maintain persistence by modifying router firmware or configuration to survive reboots.
Business
Long-term compromise of network infrastructure enables sustained espionage and data exfiltration.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05