Filtered by vendor Dlink Subscriptions
Filtered by product Dir-806 Subscriptions

Search

Switch to Advanced Search (Beta)
Total 6 CVE
CVE Vendors Products Updated CVSS v3.1
CVE-2025-4340 1 Dlink 4 Dir-806, Dir-806 Firmware, Dir-890l and 1 more 2025-05-13 6.3 Medium
A vulnerability classified as critical has been found in D-Link DIR-890L and DIR-806A1 up to 100CNb11/108B03. Affected is the function sub_175C8 of the file /htdocs/soap.cgi. The manipulation leads to command injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. This vulnerability only affects products that are no longer supported by the maintainer.
CVE-2019-10891 1 Dlink 2 Dir-806, Dir-806 Firmware 2025-01-09 9.8 Critical
An issue was discovered in D-Link DIR-806 devices. There is a command injection in function hnap_main, which calls system() without checking the parameter that can be controlled by user, and finally allows remote attackers to execute arbitrary shell commands with a special HTTP header.
CVE-2023-43130 2 D-link, Dlink 3 Dir-806 1200m11ac, Dir-806, Dir-806 Firmware 2024-11-21 9.8 Critical
D-LINK DIR-806 1200M11AC wireless router DIR806A1_FW100CNb11 is vulnerable to command injection.
CVE-2023-43129 2 D-link, Dlink 3 Dir-806 1200m11ac, Dir-806, Dir-806 Firmware 2024-11-21 9.8 Critical
D-LINK DIR-806 1200M11AC wireless router DIR806A1_FW100CNb11 is vulnerable to command injection due to lax filtering of REMOTE_PORT parameters.
CVE-2023-43128 2 D-link, Dlink 4 Dir-806 1200m11ac, Dir806a1 Fw100cnb11, Dir-806 and 1 more 2024-11-21 9.8 Critical
D-LINK DIR-806 1200M11AC wireless router DIR806A1_FW100CNb11 is vulnerable to command injection due to lax filtering of HTTP_ST parameters.
CVE-2019-10892 1 Dlink 2 Dir-806, Dir-806 Firmware 2024-11-21 N/A
An issue was discovered in D-Link DIR-806 devices. There is a stack-based buffer overflow in function hnap_main at /htdocs/cgibin. The function will call sprintf without checking the length of strings in parameters given by HTTP header and can be controlled by users. And it finally leads to a stack-based buffer overflow via a special HTTP header.