D-Link DNS-1550-04 remote_backup.cgi cgi_set_rsync_server command injection
Noroxi assessment
Priority: Monitor (action score 10/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 5.9% (FIRST EPSS); higher than 93.2% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Severity is disputed: the assigning authority (CNA) scores it 5.3, NVD 2.1.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A vulnerability has been found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR-326, DNS-340L, DNS-343, DNS-345, DNS-726-4, DNS-1100-4, DNS-1200-05 and DNS-1550-04 up to 20260205. This impacts the function cgi_recovery/cgi_backup_now/cgi_set_schedule/cgi_set_rsync_server of the file /cgi-bin/remote_backup.cgi. The manipulation leads to command injection. The attack is possible to be carried out remotely. The exploit has been disclosed to the public and may be used.
- Published
- Mar 16, 2026
- Updated
- Jun 17, 2026
- EPSS
- 5.9% · 93th percentile
- CWE
- CWE-74
Report tools
Action score
10
Monitor
Low priority for now.
- CVSS
- 8 / 40 · 2.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 5.9%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulDB
- 5.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| dlink | dns-1550-04 firmware | cpe:2.3:o:dlink:dns-1550-04_firmware |
| dlink | dns-1550-04 | cpe:2.3:h:dlink:dns-1550-04 |
| dlink | dns-315l firmware | cpe:2.3:o:dlink:dns-315l_firmware |
| dlink | dns-315l | cpe:2.3:h:dlink:dns-315l |
| dlink | dns-320 firmware | cpe:2.3:o:dlink:dns-320_firmware |
| dlink | dns-320 | cpe:2.3:h:dlink:dns-320 |
| dlink | dns-320l firmware | cpe:2.3:o:dlink:dns-320l_firmware |
| dlink | dns-320l | cpe:2.3:h:dlink:dns-320l |
| dlink | dns-320lw firmware | cpe:2.3:o:dlink:dns-320lw_firmware |
| dlink | dns-320lw | cpe:2.3:h:dlink:dns-320lw |
| dlink | dns-321 firmware | cpe:2.3:o:dlink:dns-321_firmware |
| dlink | dns-321 | cpe:2.3:h:dlink:dns-321 |
and 28 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- dlink dnr-202l firmwareup to 2026-02-05 inclusive
- dlink dnr-326 firmwareup to 2026-02-05 inclusive
- dlink dns-1100-4 firmwareup to 2026-02-05 inclusive
- dlink dns-120 firmwareup to 2026-02-05 inclusive
- dlink dns-1200-05 firmwareup to 2026-02-05 inclusive
- dlink dns-1550-04 firmwareup to 2026-02-05 inclusive
- dlink dns-315l firmwareup to 2026-02-05 inclusive
- dlink dns-320 firmwareup to 2026-02-05 inclusive
- dlink dns-320l firmwareup to 2026-02-05 inclusive
- dlink dns-320lw firmwareup to 2026-02-05 inclusive
- dlink dns-321 firmwareup to 2026-02-05 inclusive
- dlink dns-322l firmwareup to 2026-02-05 inclusive
- dlink dns-323 firmwareup to 2026-02-05 inclusive
- dlink dns-325 firmwareup to 2026-02-05 inclusive
- dlink dns-326 firmwareup to 2026-02-05 inclusive
- dlink dns-327l firmwareup to 2026-02-05 inclusive
- dlink dns-340l firmwareup to 2026-02-05 inclusive
- dlink dns-343 firmwareup to 2026-02-05 inclusive
- dlink dns-345 firmwareup to 2026-02-05 inclusive
- dlink dns-726-4 firmwareup to 2026-02-05 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulDB). Independent of NVD's CPE analysis and usually ahead of it.
D-Link DNR-202L
- 20260205affected
D-Link DNR-322L
- 20260205affected
D-Link DNR-326
- 20260205affected
D-Link DNS-1100-4
- 20260205affected
D-Link DNS-120
- 20260205affected
D-Link DNS-1200-05
- 20260205affected
D-Link DNS-1550-04
- 20260205affected
D-Link DNS-315L
- 20260205affected
D-Link DNS-320
- 20260205affected
D-Link DNS-320L
- 20260205affected
D-Link DNS-320LW
- 20260205affected
D-Link DNS-321
- 20260205affected
Same product
dlink: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-8132D-Link DNS-1550-04 HTTP POST Request webdav_mgr.cgi webdav_mgr command injection28Monitor
- CVE-2024-8129D-Link DNS-1550-04 HTTP POST Request s3.cgi cgi_s3_modify command injection28Monitor
- CVE-2024-8134D-Link DNS-1550-04 HTTP POST Request hd_config.cgi cgi_FMT_Std2R5_1st_DiskMGR command injection23Monitor
- CVE-2024-8133D-Link DNS-1550-04 HTTP POST Request hd_config.cgi cgi_FMT_R5_SpareDsk_DiskMGR command injection23Monitor
- CVE-2024-8131D-Link DNS-1550-04 HTTP POST Request apkg_mgr.cgi module_enable_disable command injection23Monitor
- CVE-2024-8130D-Link DNS-1550-04 HTTP POST Request s3.cgi cgi_s3 command injection23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- pjq123 (VulDB User)reporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-74 · Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- HTTP Request SplittingCAPEC-105likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- Format String InjectionCAPEC-135likelihood: High · High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (6 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.