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 Pligg - exploit.company
header-logo
Suggest Exploit
vendor:
Pligg
by:
Unknown
7.5
CVSS
HIGH
Cross-Site Scripting (XSS)
79
CWE
Product Name: Pligg
Affected Version From: Pligg 1.0.4
Affected Version To: Unknown (other versions may also be affected)
Patch Exists: NO
Related CWE: Unknown
CPE: a:pligg:pligg:1.0.4
Metasploit:
Other Scripts:
Platforms Tested:
Unknown

Cross-Site Scripting vulnerability in Pligg

Pligg 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 allow the attacker to steal cookie-based authentication credentials and to launch other attacks.

Mitigation:

To mitigate this vulnerability, it is recommended to implement proper input validation and sanitization routines to prevent malicious user-supplied code from being executed.
Source

Exploit-DB raw data:

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

Pligg 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 allow the attacker to steal cookie-based authentication credentials and to launch other attacks.

Pligg 1.0.4 is vulnerable; other versions may also be affected. 

http://www.example.com/search/1"><script>alert(document.cookie)</script>