dbcve.org
MailenableApplication

CVE-2025-34400

MEDIUM · 6.1 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 10.54 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
MailEnable versions prior to 10.54 contain a reflected cross-site scripting (XSS) vulnerability in the AddressesTo parameter of /Mondo/lang/sys/Forms/AddressBook.aspx. The AddressesTo value is not properly sanitized when processed via a GET request and is reflected within a <script> block in the response. By supplying a crafted payload that terminates the existing JavaScript function, inserts attacker-controlled script, and comments out remaining code, a remote attacker can execute arbitrary JavaScript in a victim’s browser when the victim attempts to send an email. Successful exploitation can redirect victims to malicious sites, steal non-HttpOnly cookies, inject arbitrary HTML or CSS, and perform actions as the authenticated user.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

MailEnable versions prior to 10.54 have a reflected XSS vulnerability in the AddressesTo parameter of /Mondo/lang/sys/Forms/AddressBook.aspx. The parameter value from GET requests is not sanitized before being reflected inside a <script> block in the response. An attacker can inject arbitrary JavaScript by terminating the existing function, adding malicious script, and commenting out remaining code.

MitigationUpgrade to MailEnable version 10.54 or later. As a compensating control, implement input validation and output encoding on the AddressesTo parameter before rendering.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MailenableApplication
Affected:< 10.54

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm MailEnable installation and version
    Locate the MailEnable installation directory (typically C:\Program Files\MailEnable or C:\Program Files (x86)\MailEnable) and check for version information in the about or version file, or check the Windows Programs and Features list.
    Affected if MailEnable is installed and the version number is less than 10.54
  2. Verify the vulnerable endpoint exists
    Check if the file AddressBook.aspx exists at the path /Mondo/lang/sys/Forms/ within the MailEnable web directory.
    Affected if The file /Mondo/lang/sys/Forms/AddressBook.aspx exists on the server
  3. Test for unsanitized reflection of AddressesTo parameter
    Send a benign GET request to the AddressBook.aspx page with the AddressesTo parameter set to a test string (for example: ?AddressesTo=test) and examine the HTTP response body to see if the value is reflected without HTML encoding.
    Affected if The AddressesTo parameter value appears in the response exactly as sent, without being HTML-encoded (for example, < becomes &lt;)
  4. Confirm reflection occurs inside a script block
    Inspect the raw HTTP response and locate whether the AddressesTo parameter value is reflected within a <script> tag in the page body.
    Affected if The parameter value is reflected inside a <script> block in the response

The environment is affected if MailEnable version is below 10.54 and the AddressesTo GET parameter is reflected without sanitization in the AddressBook.aspx page response.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.54 or later
Fixed in 10.54
Interim mitigation

Upgrade to MailEnable version 10.54 or later. As a compensating control, implement input validation and output encoding on the AddressesTo parameter before rendering.

Recommended fix High confidence

10.54

  1. 1. Back up the current MailEnable configuration and data before proceeding with the upgrade.
  2. 2. Download MailEnable version 10.54 from the official MailEnable website (mailenable.com).
  3. 3. Run the MailEnable 10.54 installer on the affected server.
  4. 4. Follow the installation wizard prompts to complete the upgrade.
  5. 5. Verify the installation was successful by checking the MailEnable version in the administration console.
  6. 6. Test that the /Mondo/lang/sys/Forms/AddressBook.aspx page no longer reflects unsanitized input in the response.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mailenable Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34400 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-34400 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data