CVE-2025-34402
BaseFortify
Publication date: 2025-12-09
Last updated on: 2025-12-09
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| mailenable | mailenable | 10.54 |
| mailenable | mailenable | to 10.54 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a reflected cross-site scripting (XSS) issue in MailEnable versions prior to 10.54. It occurs in the FieldCc parameter of the /Mondo/lang/sys/Forms/AddressBook.aspx page. The parameter is not properly sanitized when processed via a GET request and is reflected inside a <script> block in a JavaScript variable. An attacker can craft a payload that breaks the existing JavaScript function, injects malicious script, and comments out the rest of the code. This allows the attacker to execute arbitrary JavaScript in the victim's browser when they try to send an email.
How can this vulnerability impact me? :
Exploitation of this vulnerability can allow an attacker to redirect victims to malicious websites, steal non-HttpOnly cookies, inject arbitrary HTML or CSS, and perform actions on behalf of the authenticated user in the application. This can lead to unauthorized actions, data theft, and further compromise of the victim's environment.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not specify how this vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending crafted GET requests to the /Mondo/lang/sys/Forms/AddressBook.aspx page with malicious payloads in the FieldCc parameter and observing if the payload is reflected unsanitized inside the JavaScript variable var CCFieldProvided. For example, you can use curl or similar HTTP clients to send requests like: curl -v "http://<mailenable-server>/Mondo/lang/sys/Forms/AddressBook.aspx?FieldCc=<script>alert(1)</script>" and check the response for reflected script tags or payloads. Additionally, monitoring web server logs for suspicious GET requests containing script tags or unusual characters in the FieldCc parameter can help detect exploitation attempts. [2]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to upgrade MailEnable to version 10.54 or later, where this reflected XSS vulnerability in the FieldCc parameter has been fixed. If upgrading immediately is not possible, consider implementing web application firewall (WAF) rules to block or sanitize requests containing suspicious script payloads in the FieldCc parameter. Additionally, educate users to be cautious when interacting with the affected interface and monitor for suspicious activity. Applying security best practices such as enforcing secure cookies and other hardening measures as described in recent MailEnable releases can also help reduce risk. [2, 3]