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 Vulnerabilities in Scoop - exploit.company
header-logo
Suggest Exploit
vendor:
Scoop
by:
Unknown
7.5
CVSS
HIGH
Cross-Site Scripting
79
CWE
Product Name: Scoop
Affected Version From: Scoop 1.1 RC1
Affected Version To: Unknown
Patch Exists: NO
Related CWE:
CPE: a:scoop_project:scoop:1.1_rc1
Metasploit:
Other Scripts:
Platforms Tested:
2005

Cross-Site Scripting Vulnerabilities in Scoop

Scoop is prone to multiple cross-site scripting vulnerabilities. These issues are due to a failure in the application to properly sanitize user-supplied input. An attacker may leverage these issues 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.

Mitigation:

To mitigate these vulnerabilities, it is recommended to implement proper input validation and sanitization techniques to prevent the execution of arbitrary script code.
Source

Exploit-DB raw data:

source: https://www.securityfocus.com/bid/16014/info
 
Scoop is prone to multiple cross-site scripting vulnerabilities. These issues are due to a failure in the application to properly sanitize user-supplied input.
 
An attacker may leverage these issues 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.
 
Scoop 1.1 RC1 is reportedly vulnerable to these issues; prior versions may also be affected. 

http://www.example.com/story/2005/11/4/184932/452[XSS]
http://www.example.com/story/2005/11/4/184932[XSS]
http://www.example.com/story/2005/11/4[XSS]
http://www.example.com/story/2005/11[XSS]
http://www.example.com/story/2005[XSS]
http://www.example.com/story/[XSS]