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 IBM WebSphere ILOG JRules - exploit.company
header-logo
Suggest Exploit
vendor:
IBM WebSphere ILOG JRules
by:
7.5
CVSS
HIGH
Cross-Site Scripting (XSS)
79
CWE
Product Name: IBM WebSphere ILOG JRules
Affected Version From: 6.7
Affected Version To: 6.7
Patch Exists: NO
Related CWE:
CPE: a:ibm:websphere_ilog_jrules:6.7
Metasploit:
Other Scripts:
Platforms Tested:

Cross-Site Scripting Vulnerability in IBM WebSphere ILOG JRules

IBM WebSphere ILOG JRules is vulnerable to a cross-site scripting (XSS) vulnerability. This vulnerability occurs due to the application's failure to properly sanitize user-supplied input. An attacker can exploit this vulnerability to execute arbitrary script code in the browser of an unsuspecting user, potentially leading to the theft of cookie-based authentication credentials and other malicious activities.

Mitigation:

To mitigate this vulnerability, it is recommended to apply the latest security patches or updates provided by IBM. Additionally, input validation and output encoding should be implemented to properly sanitize user-supplied input and prevent XSS attacks.
Source

Exploit-DB raw data:

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

IBM WebSphere ILOG JRules is prone to a cross-site scripting vulnerability because it fails to properly sanitize user-supplied input.

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

The issue affects version 6.7. 


The following example input to the URI is available:
?<script>alert(31521);</script>?