CVE-2026-4197 | D-Link DNS-1550-04 download_mgr.cgi RSS_Item_List command injection

Exp

A vulnerability was 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. Affected is the function RSS_Get_Update_Status/RSS_Update/RSS_Channel_AutoDownlaod/RSS_Add/RSS_Channel_Item_Downlaod/RSS_History_Item_List/RSS_Item_List of the file /cgi-bin/download_mgr.cgi. The manipulation results in command injection. The attack may be performed from remote. The exploit has been made public and could be used.

Published: 2026-03-16 Last update: 2026-04-29 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-4197 is rated Exploit Available (50/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.08%). 2 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2026-4197

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2026-4197

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-20 0.51% 0.08% -0.43%
2 2026-03-19 0.40% 0.51% +0.10%
3 2026-03-16 — 0.40% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-4197

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
2.1 4.0 LOW
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 Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network.
Attack complexity (AC:L)
Exploitation conditions are straightforward and stable.
Attack requirements (AT:N)
No additional preconditions are required beyond normal reachability.
Privileges required (PR:L)
Low privileges are required.
User interaction (UI:N)
No user interaction is required.
Vulnerable system confidentiality impact (VC:L)
Limited confidentiality impact on the vulnerable system.
Vulnerable system integrity impact (VI:L)
Limited integrity impact on the vulnerable system.
Vulnerable system availability impact (VA:L)
Limited availability impact on the vulnerable system.
Subsequent system confidentiality impact (SC:N)
No confidentiality impact on subsequent systems.
Subsequent system integrity impact (SI:N)
No integrity impact on subsequent systems.
Subsequent system availability impact (SA:N)
No availability impact on subsequent systems.
Exploit maturity (threat) (E:P)
Proof-of-concept: public PoC exists; no reported exploitation and no known simplification tools.
Confidentiality requirement (CR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Integrity requirement (IR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Availability requirement (AR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Modified attack vector (MAV:X)
Not defined: scoring uses the Base Attack Vector (AV).
Modified attack complexity (MAC:X)
Not defined: scoring uses the Base Attack Complexity (AC).
Modified attack requirements (MAT:X)
Not defined: scoring uses the Base Attack Requirements (AT).
Modified privileges required (MPR:X)
Not defined: scoring uses the Base Privileges Required (PR).
Modified user interaction (MUI:X)
Not defined: scoring uses the Base User Interaction (UI).
Modified vulnerable system confidentiality impact (MVC:X)
Not defined: scoring uses the Base VC metric.
Modified vulnerable system integrity impact (MVI:X)
Not defined: scoring uses the Base VI metric.
Modified vulnerable system availability impact (MVA:X)
Not defined: scoring uses the Base VA metric.
Modified subsequent system confidentiality impact (MSC:X)
Not defined: scoring uses the Base SC metric.
Modified subsequent system integrity impact (MSI:X)
Not defined: scoring uses the Base SI metric.
Modified subsequent system availability impact (MSA:X)
Not defined: scoring uses the Base SA metric.
Safety (supplemental) (S:X)
Not evaluated.
Automatable (supplemental) (AU:X)
Not evaluated.
Recovery (supplemental) (R:X)
Not evaluated.
Value density (supplemental) (V:X)
Not evaluated.
Vulnerability response effort (supplemental) (RE:X)
Not evaluated.
Provider urgency (supplemental) (U:X)
Not evaluated.
 — — [email protected]
6.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 2.8 3.4 [email protected]
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
6.5 2.0 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.0 6.4 [email protected]

Weakness enumeration for CVE-2026-4197

Affected software / configurations for CVE-2026-4197

Vendor Product Version Raw CPE
dlink dnr-202l_firmware <= 2026-02-05 cpe:2.3:o:dlink:dnr-202l_firmware:*:*:*:*:*:*:*:*
dlink dnr-326_firmware <= 2026-02-05 cpe:2.3:o:dlink:dnr-326_firmware:*:*:*:*:*:*:*:*
dlink dns-1100-4_firmware <= 2026-02-05 cpe:2.3:o:dlink:dns-1100-4_firmware:*:*:*:*:*:*:*:*
dlink dns-120_firmware <= 2026-02-05 cpe:2.3:o:dlink:dns-120_firmware:*:*:*:*:*:*:*:*
dlink dns-1200-05_firmware <= 2026-02-05 cpe:2.3:o:dlink:dns-1200-05_firmware:*:*:*:*:*:*:*:*
dlink dns-1550-04_firmware <= 2026-02-05 cpe:2.3:o:dlink:dns-1550-04_firmware:*:*:*:*:*:*:*:*
dlink dns-315l_firmware <= 2026-02-05 cpe:2.3:o:dlink:dns-315l_firmware:*:*:*:*:*:*:*:*
dlink dns-320_firmware <= 2026-02-05 cpe:2.3:o:dlink:dns-320_firmware:*:*:*:*:*:*:*:*
dlink dns-320l_firmware <= 2026-02-05 cpe:2.3:o:dlink:dns-320l_firmware:*:*:*:*:*:*:*:*
dlink dns-320lw_firmware <= 2026-02-05 cpe:2.3:o:dlink:dns-320lw_firmware:*:*:*:*:*:*:*:*
dlink dns-321_firmware <= 2026-02-05 cpe:2.3:o:dlink:dns-321_firmware:*:*:*:*:*:*:*:*
dlink dns-322l_firmware <= 2026-02-05 cpe:2.3:o:dlink:dns-322l_firmware:*:*:*:*:*:*:*:*
dlink dns-323_firmware <= 2026-02-05 cpe:2.3:o:dlink:dns-323_firmware:*:*:*:*:*:*:*:*
dlink dns-325_firmware <= 2026-02-05 cpe:2.3:o:dlink:dns-325_firmware:*:*:*:*:*:*:*:*
dlink dns-326_firmware <= 2026-02-05 cpe:2.3:o:dlink:dns-326_firmware:*:*:*:*:*:*:*:*
dlink dns-327l_firmware <= 2026-02-05 cpe:2.3:o:dlink:dns-327l_firmware:*:*:*:*:*:*:*:*
dlink dns-340l_firmware <= 2026-02-05 cpe:2.3:o:dlink:dns-340l_firmware:*:*:*:*:*:*:*:*
dlink dns-343_firmware <= 2026-02-05 cpe:2.3:o:dlink:dns-343_firmware:*:*:*:*:*:*:*:*
dlink dns-345_firmware <= 2026-02-05 cpe:2.3:o:dlink:dns-345_firmware:*:*:*:*:*:*:*:*
dlink dns-726-4_firmware <= 2026-02-05 cpe:2.3:o:dlink:dns-726-4_firmware:*:*:*:*:*:*:*:*

References for CVE-2026-4197

URL Tags
https://github.com/wudipjq/my_vuln/blob/main/D-Link8/vuln_102/102.md Exploit Third Party Advisory
https://github.com/wudipjq/my_vuln/blob/main/D-Link8/vuln_103/103.md Exploit Third Party Advisory
https://vuldb.com/?ctiid.351109 Permissions Required VDB Entry
https://vuldb.com/?id.351109 Third Party Advisory VDB Entry
https://vuldb.com/?submit.769864 Third Party Advisory VDB Entry
https://vuldb.com/?submit.769865 Third Party Advisory VDB Entry
https://vuldb.com/?submit.769866 Third Party Advisory VDB Entry
https://vuldb.com/?submit.769867 Third Party Advisory VDB Entry
https://vuldb.com/?submit.769868 Third Party Advisory VDB Entry
https://vuldb.com/?submit.769869 Third Party Advisory VDB Entry
https://vuldb.com/?submit.769870 Third Party Advisory VDB Entry
https://vuldb.com/?submit.770363 Third Party Advisory VDB Entry
https://vuldb.com/?submit.770364 Third Party Advisory VDB Entry
https://www.dlink.com/ Product
cvelogic Threat Intelligence