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 GMailSite - exploit.company
header-logo
Suggest Exploit
vendor:
GMailSite
by:
5.5
CVSS
MEDIUM
Cross-Site Scripting (XSS)
79
CWE
Product Name: GMailSite
Affected Version From: GMailSite 1.0.4 and prior
Affected Version To:
Patch Exists: NO
Related CWE:
CPE:
Metasploit:
Other Scripts:
Platforms Tested:

Cross-Site Scripting Vulnerability in GMailSite

The GMailSite web application is vulnerable to a cross-site scripting attack. An attacker can inject arbitrary script code into the browser of a user visiting the affected site, potentially allowing them to steal authentication credentials and perform other malicious actions.

Mitigation:

To mitigate this vulnerability, it is recommended to implement input validation and output encoding to prevent the execution of malicious script code. Additionally, keeping the application up to date with the latest security patches is advised.
Source

Exploit-DB raw data:

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

GMailSite is prone to a cross-site scripting vulnerability.

An attacker may leverage this issue 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.

GMailSite 1.0.4 and prior versions are affected by this issue. GFHost 0.4.2 and prior versions are also vulnerable.

http://www.example.com/?lng=es"><script>alert(document.cookie)</script>
http://www.example.com/index.php?lng=es"><script>alert(document.cookie)</script>