D-Link DNS-1550-04 up to 20260205 /cgi-bin/app_mgr.cgi command injection

Summaryinfo

A vulnerability marked as critical has been reported 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 affects the function cgi_refresh_db/FTP_Server_BlockIP_Add/FTP_Server_BlockIP_Del of the file /cgi-bin/app_mgr.cgi. Performing a manipulation results in command injection. This vulnerability is reported as CVE-2026-4205. The attack is possible to be carried out remotely. Moreover, an exploit is present.

Detailsinfo

A vulnerability classified as critical 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 affects the function cgi_refresh_db/FTP_Server_BlockIP_Add/FTP_Server_BlockIP_Del of the file /cgi-bin/app_mgr.cgi. The manipulation with an unknown input leads to a command injection vulnerability. CWE is classifying the issue as CWE-77. The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-4205. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details and a public exploit are known. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/21/2026). MITRE ATT&CK project uses the attack technique T1202 for this issue.

The exploit is shared for download at github.com. It is declared as proof-of-concept.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• D-Link

Name

• DNR-202L
• DNR-322L
• DNR-326
• DNS-120
• DNS-315L
• DNS-320
• DNS-320L
• DNS-320LW
• DNS-321
• DNS-323
• DNS-325
• DNS-326
• DNS-327L
• DNS-340L
• DNS-343
• DNS-345
• DNS-726-4
• DNS-1100-4
• DNS-1200-05
• DNS-1550-04

Version

• 20260205

License

• commercial

Website

• Vendor: https://www.dlink.com/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Submitinfo

Accepted

• Submit #770410: D-Link DNS-120/202L/315L/320/320L/320LW/321/322L/323/325/326/327L/326/340L/343/345/726-4/1100-4/1200-05/1550-04 up to 20260205 Command Injection (by Bond)

Duplicate

• Submit #XXXXXX: X-xxxx Xxx-xxx/xxxx/xxxx/xxx/xxxx/xxxxx/xxx/xxxx/xxx/xxx/xxx/xxxx/xxx/xxxx/xxx/xxx/xxx-x/xxxx-x/xxxx-xx/xxxx-xx Xx Xx Xxxxxxxx Xxxxxxx Xxxxxxxxx (by Bond)
• Submit #XXXXXX: X-xxxx Xxx-xxx/xxxx/xxxx/xxx/xxxx/xxxxx/xxx/xxxx/xxx/xxx/xxx/xxxx/xxx/xxxx/xxx/xxx/xxx-x/xxxx-x/xxxx-xx/xxxx-xx Xx Xx Xxxxxxxx Xxxxxxx Xxxxxxxxx (by Bond)

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion