dbcve.org
MailenableApplication

CVE-2025-34401

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 FieldBcc parameter of /Mondo/lang/sys/Forms/AddressBook.aspx. The FieldBcc value is not properly sanitized when processed via a GET request and is reflected inside a <script> block in the JavaScript variable var BCCFieldProvided. By supplying a crafted payload that terminates the existing LoadCurAddresses() function, inserts attacker-controlled script, and comments out remaining code, a remote attacker can execute arbitrary JavaScript in a victim’s browser during normal email composition. 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 /Mondo/lang/sys/Forms/AddressBook.aspx. The FieldBcc GET parameter is not sanitized and is directly reflected inside a <script> block as the var BCCFieldProvided value, allowing attackers to inject arbitrary JavaScript by terminating the existing LoadCurAddresses() function and commenting out remaining code.

MitigationUpgrade to MailEnable version 10.54 or later. As a temporary workaround, disable or restrict access to the AddressBook.aspx page until the patch can be applied.

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
    Check if MailEnable is installed on the system by looking for the MailEnable installation directory (commonly at C:\Program Files\MailEnable or C:\Program Files (x86)\MailEnable) or check running services for MailEnable services.
    Affected if MailEnable is installed on the server.
  2. Identify installed MailEnable version
    Locate the MailEnable version information. This is typically found in the MailEnable administration GUI under 'About' or in registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\MailEnable or within the installation directory in version files.
    Affected if The installed version is any version prior to 10.54.
  3. Verify vulnerable endpoint exists
    Check if the file AddressBook.aspx exists in the /Mondo/lang/sys/Forms/ path of the MailEnable web installation. This is typically under the MailEnable web server root directory.
    Affected if The AddressBook.aspx file exists and is accessible via the web server.
  4. Check FieldBcc parameter handling
    Send a test request to /Mondo/lang/sys/Forms/AddressBook.aspx with a crafted FieldBcc parameter (e.g., FieldBcc=</script><script>alert(1)</script>) and inspect the response to verify if the value is reflected without proper HTML encoding.
    Affected if The FieldBcc GET parameter value is reflected in the response without HTML encoding inside the <script> block as BCCFieldProvided.

The server is affected if MailEnable versions prior to 10.54 are installed and the AddressBook.aspx page is accessible with unescaped reflection of the FieldBcc parameter.

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 temporary workaround, disable or restrict access to the AddressBook.aspx page until the patch can be applied.

Recommended fix High confidence

10.54

  1. Obtain MailEnable version 10.54 from the official vendor at mailenable.com
  2. Follow MailEnable's standard upgrade procedure to update the installation to version 10.54
  3. Verify the update was successful by confirming the installed version is 10.54 or higher

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

Fix this in Mailenable Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34401 — 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-34401 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