Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-pagenavi domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/u918112125/domains/exploit.company/public_html/wp-includes/functions.php on line 6114
Cross-Site Scripting Vulnerability in D-Link DSL-G624T - exploit.company
header-logo
Suggest Exploit
vendor:
DSL-G624T
by:
Unknown
5.5
CVSS
MEDIUM
Cross-Site Scripting
79
CWE
Product Name: DSL-G624T
Affected Version From: D-Link DSL-G624T firmware versions prior to the patched version
Affected Version To: D-Link DSL-G624T firmware versions prior to the patched version
Patch Exists: YES
Related CWE: CVE-2007-1525
CPE: h:d-link:dsl-g624t
Metasploit:
Other Scripts:
Platforms Tested:
2007

Cross-Site Scripting Vulnerability in D-Link DSL-G624T

The D-Link DSL-G624T router is prone to a cross-site scripting vulnerability. The issue occurs due to a failure to properly sanitize user-supplied input. An attacker can exploit this vulnerability to execute arbitrary script code in the browser of a victim user, within the context of the affected site. This can potentially lead to the theft of cookie-based authentication credentials and facilitate other malicious activities.

Mitigation:

To mitigate this vulnerability, users are advised to update to the latest firmware version provided by D-Link. Additionally, it is recommended to disable remote management and restrict access to the router's administration interface to trusted networks or IP addresses.
Source

Exploit-DB raw data:

source: https://www.securityfocus.com/bid/23802/info

D-Link DSL-G624T is prone to a cross-site scripting vulnerability. This issue is due to a failure to properly sanitize user-supplied input.

An attacker may leverage this issue to have arbitrary script code execute in the browser of an unsuspecting user in the context of the affected site. This may help the attacker steal cookie-based authentication credentials and launch other attacks. 

http://www.example.com/cgi-bin/webcm?getpage=../html/home/home_RelaodHref.htm&var:RelaodHref=a"%20==%20"a"){alert("XSS")}}</script>