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
Multiple Remote Vulnerabilities in 04WebServer - exploit.company
header-logo
Suggest Exploit
vendor:
04WebServer
by:
5.5
CVSS
MEDIUM
Cross-Site Scripting (XSS), Log Injection
79, 117
CWE
Product Name: 04WebServer
Affected Version From:
Affected Version To:
Patch Exists: NO
Related CWE:
CPE:
Metasploit:
Other Scripts:
Platforms Tested:

Multiple Remote Vulnerabilities in 04WebServer

The vulnerabilities in 04WebServer allow for cross-site scripting attacks and log injection due to improper input sanitization. An attacker can exploit these issues to execute arbitrary scripts on the affected server and inject arbitrary characters into log files, potentially leading to corruption.

Mitigation:

To mitigate these vulnerabilities, it is recommended to sanitize user input properly. Implementing input validation and output encoding can help prevent cross-site scripting attacks. Additionally, logging mechanisms should be properly implemented to avoid log injection.
Source

Exploit-DB raw data:

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

Multiple remote vulnerabilities reportedly affect 04WebServer. These issues are due to a failure of the application to properly sanitize user-supplied input.

An attacker may leverage these issues to carry out cross-site scripting attacks against any Web sites hosted on the affected server and to inject arbitrary characters into log files, potentially leading to corruption.

To leverage the cross-site scripting issue:
http://www.example.com/<script>alert('XSS');</script>

To inject the log entry '[22;45;24] <192.168.1.3> (74,632) [?.?.?.?I?.?.?.?.?.] GET /hack' into the log file the following request is sufficient:
http://www.example.com/a%0a[22;45;24]%20<192.168.1.3>%20(74,632)%20[%90%b3%8f%ed%82%c9%8f%49%97%b9%82%b5%82%dc%82%b5%82%bd]%20GET%20/hack