Threats / D-Link / CVE-2022-26258
CVE-2022-26258
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
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-084EPSS 0.91981 (verify live)5CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreReported 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).
Probability (EPSS)
EPSS 0.91981 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: D-Link, DIR-820L. 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-78 OS 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: yes · 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 165 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.
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 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’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by mitreCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.