CVE-2025-34401
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 | * |
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 FieldBcc 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 JavaScript <script> block. 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 during normal email composition.
How can this vulnerability impact me? :
Exploitation of this vulnerability can allow a remote attacker to execute arbitrary JavaScript in the victim's browser. This can lead to redirecting victims to malicious websites, stealing non-HttpOnly cookies, injecting arbitrary HTML or CSS, and performing actions on behalf of the authenticated user, potentially compromising user data and session integrity.
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 vulnerable endpoint /Mondo/lang/sys/Forms/AddressBook.aspx with malicious payloads in the FieldBcc parameter and observing if the payload is reflected unsanitized inside the JavaScript variable var BCCFieldProvided. For example, you can use curl or similar HTTP clients to test the endpoint: curl -v "http://<mailenable-server>/Mondo/lang/sys/Forms/AddressBook.aspx?FieldBcc=<script>alert(1)</script>" and check the response for reflected script tags or payloads. Additionally, web vulnerability scanners that detect reflected XSS vulnerabilities can be used against this URL and parameter to identify the issue. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include upgrading MailEnable to version 10.54 or later, where this reflected XSS vulnerability has been fixed. If upgrading is not immediately possible, consider applying web application firewall (WAF) rules to block or sanitize requests containing suspicious scripts in the FieldBcc parameter. Also, educate users to be cautious of suspicious links and avoid interacting with untrusted email composition pages. Applying secure cookie flags and other security hardening measures as described in recent MailEnable releases can help reduce impact. [2, 3]
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.