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 in LiteSpeed Web Server - exploit.company
header-logo
Suggest Exploit
vendor:
LiteSpeed Web Server
by:
5.5
CVSS
MEDIUM
Cross-Site Scripting (XSS)
79
CWE
Product Name: LiteSpeed Web Server
Affected Version From:
Affected Version To:
Patch Exists: YES
Related CWE:
CPE:
Metasploit:
Other Scripts:
Platforms Tested:

Cross-Site Scripting in LiteSpeed Web Server

The LiteSpeed Web Server is vulnerable to a cross-site scripting (XSS) attack. The vulnerability exists because the application fails to properly sanitize user-supplied input. An attacker can exploit this vulnerability by injecting arbitrary script code into a specific parameter of the affected site's URL. This can lead to the execution of malicious scripts in the victim's browser, potentially allowing the attacker to steal authentication credentials and launch further attacks.

Mitigation:

To mitigate this vulnerability, it is recommended to sanitize and validate all user-supplied input before using it in the application. Additionally, web application firewalls (WAFs) can be employed to detect and block XSS attacks.
Source

Exploit-DB raw data:

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

LiteSpeed Web Server is prone to a cross-site scripting vulnerability. This issue is due to a failure in the application to properly sanitize user-supplied input.

An attacker may leverage this issue to have arbitrary script code executed in the browser of an unsuspecting user in the context of the affected site. This may facilitate the theft of cookie-based authentication credentials as well as other attacks. 

http://www.example.com:7080/admin/config/confMgr.php?m=al_adminListener%3Cscript%3Ealert(document.cookie)%3C/script%3E