CVE-2025-34399
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 AddressesCc 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 out of the existing JavaScript function, injects malicious script, and disables the rest of the code. When a victim sends an email, the malicious script executes in their browser, allowing the attacker to run arbitrary JavaScript.
How can this vulnerability impact me? :
Exploitation of this vulnerability can allow an attacker to redirect victims to malicious websites, steal cookies that are not marked as HttpOnly, inject arbitrary HTML or CSS, and perform actions on behalf of the authenticated user. This can lead to account compromise, data theft, and unauthorized actions within the affected MailEnable environment.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the AddressesCc parameter of the /Mondo/lang/sys/Forms/AddressBook.aspx page for reflected cross-site scripting (XSS). You can perform a GET request with a crafted payload in the AddressesCc parameter that attempts to inject JavaScript code and observe if the payload is reflected unsanitized within the JavaScript variable var sAddrCc. For example, using curl or a web proxy tool, you can send a request like: curl "http://<target>/Mondo/lang/sys/Forms/AddressBook.aspx?AddressesCc=<script>alert(1)</script>" and check if the script is executed or reflected in the response. Additionally, web vulnerability scanners that test for reflected XSS on GET parameters can be used to detect this 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 vulnerability has been fixed. If upgrading is not immediately possible, consider implementing web application firewall (WAF) rules to block or sanitize requests containing suspicious payloads in the AddressesCc parameter. Additionally, educate users to be cautious when clicking on links that include the AddressesCc parameter and monitor for suspicious activity. Applying security best practices such as enforcing secure cookies and limiting user privileges can also help reduce impact. [2, 3]