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 Cross-Site Scripting Vulnerabilities in Active Calendar - exploit.company
header-logo
Suggest Exploit
vendor:
Active Calendar
by:
7.5
CVSS
HIGH
Cross-Site Scripting (XSS)
79
CWE
Product Name: Active Calendar
Affected Version From: 1.2.2000
Affected Version To:
Patch Exists: NO
Related CWE:
CPE:
Metasploit:
Other Scripts:
Platforms Tested:

Multiple Cross-Site Scripting Vulnerabilities in Active Calendar

Active Calendar is prone to multiple cross-site scripting vulnerabilities because the application fails to sufficiently sanitize user-supplied input. An attacker may leverage these issues 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 these vulnerabilities, it is recommended to sanitize and validate all user-supplied input before using it in the application.
Source

Exploit-DB raw data:

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

Active Calendar is prone to multiple cross-site scripting vulnerabilities because the application fails to sufficiently sanitize user-supplied input.

An attacker may leverage these issues 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.

Active Calendar 1.2.0 is vulnerable; other versions (or products that include Active Calendar) may also be affected. 

http://www.example.com/test.php/"><script>document.body.innerHTML=&#039;XSS&#039;;</script>