Sushant Mane

Name of the Vulnerable Software and Affected Versions: TP-Link Archer C50 (affected versions not specified) Description: The issue is related to the improper signature verification mechanism in the firmware upgrade process at the web interface of the TP-Link Archer C50. This allows an attacker with administrative privileges within the router's Wi-Fi range to exploit the vulnerability by uploading and executing malicious firmware, potentially leading to the complete compromise of the targeted device. The exploitation can result in the execution of arbitrary code and may cause a denial of service. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability.

This issue exists due to insufficient validation of user-supplied input for the `DDNS Username` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, potentially allowing them to perform stored XSS attacks on the targeted system.

This issue exists due to insufficient validation of user-supplied input for the `Device Name` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

This issue exists due to the transmission of authentication credentials in plaintext over the network. A remote attacker could exploit this by eavesdropping on the victim’s network traffic to extract the `username` and `password` from the web interface (Login Page) of the targeted system.

This issue exists due to the transmission of authentication credentials in plaintext over the network. A remote attacker could exploit this by eavesdropping on the victim’s network traffic to extract the `username` and `password` from the web interface, specifically the Password Reset Page, of the targeted system.

This issue is due to insufficient validation of user-supplied input for the `Add Downstream Frequency` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, potentially allowing a Denial of Service (DoS) attack on the targeted system.

This issue is due to insufficient validation of user-supplied input for the `Set Upstream Channel ID (UCID)` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, potentially allowing them to perform a Denial of Service (DoS) attack on the targeted system.

This issue is due to insufficient validation of user-supplied input for the `Traceroute` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

This issue exists due to insufficient validation of user-supplied input for the `Time Server 1` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

The issue exists due to insufficient validation of user-supplied input for the `Time Server 2` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

This issue exists due to insufficient validation of user-supplied input for the `Time Server 3` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

This issue is due to insufficient validation of user-supplied input for the `Description` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

This issue exists due to insufficient validation of user-supplied input for the `URL` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

This issue exists due to insufficient validation of user-supplied input for the `Contact Email Address` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

This issue is due to insufficient validation of user-supplied input for the `SMTP Server Name` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

This issue exists due to insufficient validation of user-supplied input for the `SMTP Username` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, potentially allowing them to perform stored XSS attacks on the targeted system.

The issue exists due to insufficient validation of user-supplied input for the `SMTP Password` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, potentially allowing them to perform stored XSS attacks on the targeted system.

The issue is due to insufficient validation of user-supplied input for the `DDNS Password` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, potentially allowing stored XSS attacks on the targeted system.

This issue is due to insufficient validation of user-supplied input for the `Hostname` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.

This issue exists due to insufficient validation of user-supplied input for the `IPsec Tunnel Name` parameter at the web interface. A remote attacker could exploit this by supplying specially crafted input to the parameter, allowing them to perform stored XSS attacks on the targeted system.