basicsecurity.net
Proof, not just disclosure.
Threats / D-Link / CVE-2022-26258
CVE-2022-26258 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

D-Link DIR-820L vulnerability

D-Link DIR-820L contains an OS command injection vulnerability in the Device Name parameter of /lan.asp, enabling unauthenticated remote code execution.

Verdict

Today item — known-exploited.

An attacker can inject arbitrary OS commands through the Device Name field in the web interface, achieving remote code execution on the device. This vulnerability is actively exploited in the wild and poses critical risk to network infrastructure.

CISA KEV Yes · 2022-09-083EPSS 0.81195 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
3 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-09-08).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.81195 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: D-Link, DIR-820L. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-78 OS Command Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious Device Name parameter containing shell metacharacters to break out of the intended command context.
Business
Network device is compromised, potentially serving as an entry point for lateral movement into the organization's infrastructure.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I send an HTTP request to /lan.asp with injected OS commands embedded in the Device Name field without requiring authentication.
Business
Attacker gains code execution privileges equivalent to the web service process, enabling device takeover and data exfiltration.
3

Lateral reach — past segmentation narrative 3

Attacker
I establish persistent access by modifying device configuration or installing backdoors through the compromised command execution.
Business
Router becomes a persistent threat actor foothold, enabling ongoing network surveillance, traffic interception, and further compromise of connected systems.
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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 3 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by mitre (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.