CVE-2022-26258
D-Link DIR-820L 1.05B03 was discovered to contain remote command execution (RCE) vulnerability via HTTP POST to get set ccp.
- CVSS
- 9.8Criticalscored by CISA
- Exploited in the wild
- Yes, in CISA KEV since 8 Sept 2022CISA deadline for US federal agencies: 29 Sept 2022
- EPSS
- 91.6%chance of exploitation in the next 30 daystop 0.2% of scored CVEsFIRST score of 11 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 28 Mar 2022analysed here 12 Nov 2026
Do first. The impacted product is end-of-life and should be disconnected if still in use. (CISA's required action for this KEV entry)
Summary
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
Products named in our analysis
- dlink:dir-820l_firmware
Fix and mitigation
WAF and other mitigations
Can a WAF block it? Partly. The vulnerability is triggered by an HTTP POST request to a specific endpoint 'get set ccp' which allows remote command execution. The malicious input likely contains command injection syntax that could be detected, but such syntax might sometimes appear in legitimate requests, making filtering only partly reliable. A custom WAF rule can filter HTTP POST to get set ccp with command injection syntax, but attackers can vary the request. No tracked WAF vendor has published a rule for this CVE yet.
What a custom rule would match: HTTP POST to get set ccp with command injection syntax
Also consider: patch · custom WAF rule · shlex/execve-style APIs
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Listed since 8 Sept 2022.
- CISA due date
- 29 Sept 2022, the remediation deadline for US federal agencies
- CISA required action
- The impacted product is end-of-life and should be disconnected if still in use.
- Public exploit code
- None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- CISA SSVC
- exploitation active, automatable yes, technical impact totalAssessed by CISA 29 Jan 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Timeline
- 28 Mar 2022Published
- 8 Sept 2022Added to CISA KEV (exploited in the wild)164 days (about 5 months) later
- 29 Sept 2022CISA remediation due date (US federal agencies)21 days later
- 29 Jan 2025CISA SSVC assessment: exploitation active854 days (about 2 years) later
- 9 Jul 2026CVE record last updated525 days (about 1 year) later
- 12 Nov 2026Analysed by vulneraibility.com126 days (about 4 months) later
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
| Metric | Value | What it means |
|---|---|---|
| Attack vector | NetworkReachable over the internet or any routable network. | Reachable over the internet or any routable network. |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | NoneThe attacker needs no prior access. | The attacker needs no prior access. |
| User interaction | NoneNo victim action needed. | No victim action needed. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | HighComplete modification possible. | Complete modification possible. |
| Availability | HighFull outage possible. | Full outage possible. |
Common questions
Is CVE-2022-26258 being exploited?
Yes. CVE-2022-26258 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2022-26258?
CVE-2022-26258 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2022-26258?
Yes. A fix has been recorded for CVE-2022-26258. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2022-26258 affect?
CVE-2022-26258 affects dlink:dir-820l_firmware. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
4 references in the CVE record, grouped by the tags the record gives them.
Other links (4)
- dlink.com /en/security-bulletin/
- github.com /skyedai910/Vuln/tree/master/DIR-820L/command_execution_0
- github.com /zhizhuoshuma/cve_info_data/blob/ccaed4b94ba762eb8a8e003bfa762a7754b8182e/Vuln/V
- cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-26258
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.