CVE-2022-26258 — D-Link DIR-820L Remote Code Execution Vulnerability
D-Link DIR-820L 1.05B03 was discovered to contain remote command execution (RCE) vulnerability via HTTP POST to get set ccp.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- EPSS 91.6% (30-day exploitation probability)+15
- Technical severity (critical)+10
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
CISA required action CISA
The impacted product is end-of-life and should be disconnected if still in use.
US federal deadline: Sep 29, 2022 — passed 1477 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Dlink Dir-820l Firmware).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Dlink | Dir-820l Firmware | version 1.05b03 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database |
| 9.8 | CVSS 3.1 | Critical | — | — | GitHub, Inc. via GitHub Security Advisories |
| 9.8 | CVSS 3.1 | Critical | — | — | CISA-ADP via CVE Program (cve.org) e CISA ADP |
| 7.5 | CVSS 2.0 | High | 10.0 | 6.4 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
EPSS over time FIRST
Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 91.63%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Look for parameters with command/query metacharacters and unexpected child processes of the service.
- Hunt retroactively in logs from before Sep 8, 2022 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Record published
- Affected products added · dlink/dir-820l firmware
- CVSS changed · 9.8
- Source status changed · → Analyzed
- Added to CISA KEV (detected)
- Record created in this database
- 2022
- Added to CISA KEV catalog
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
9 on the record
- www.dlink.com/en/security-bulletin/
- www.cisa.gov/known-exploited-vulnerabilities-catalog
- www.dlink.com/en/security-bulletin
- dlink.com
- nvd.nist.gov/vuln/detail/CVE-2022-26258
- github.com/advisories/GHSA-qf97-3r3x-x56v
- github.com/zhizhuoshuma/cve_info_data/blob/ccaed4b94ba762eb8a8e003bfa762a7754b81
- github.com/skyedai910/Vuln/tree/master/DIR-820L/command_execution_0
- dir-820l.com
Elsewhere on this site
Related CVEs (same products)
- High CVE-2025-52079 Improper Access Control in Dlink Dir-820l Firmware Oct 21, 2025
- Critical CVE-2023-25280 D-Link DIR-820 Router OS Command Injection Vulnerability KEV Mar 15, 2023
- Critical CVE-2021-45382 D-Link Multiple Routers Remote Code Execution Vulnerability KEV Feb 17, 2022
- Critical CVE-2015-1187 D-Link and TRENDnet Multiple Devices Remote Code Execution Vulnerability KEV Sep 21, 2017
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2022-26258 is "D-Link DIR-820L Remote Code Execution Vulnerability", rated Critical. It affects Dir-820l Firmware (Dlink); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 9.8 describes technical severity. EPSS 91.63% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.