dbcve.org
MailenableApplication

CVE-2025-34408

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 Added parameter of /Mondo/lang/sys/Forms/MAI/AddRecipientsResult.aspx. The Added value is not properly sanitized when processed via a GET request and is reflected in the response, allowing an attacker to break out of existing markup and inject arbitrary script. A remote attacker can supply a crafted payload that closes an existing HTML list element, inserts attacker-controlled JavaScript, and comments out remaining code, leading to script execution in a victim’s browser when the victim visits a malicious link. 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 AddRecipientsResult.aspx page. The 'Added' GET parameter is not sanitized before being reflected in the HTTP response, allowing attackers to break out of existing HTML markup and inject arbitrary JavaScript by crafting a payload that closes existing elements, inserts malicious script, and comments out the remainder.

MitigationUpgrade to MailEnable version 10.54 or later, which contains the patch for this vulnerability. As a temporary workaround, disable or restrict access to the affected /Mondo/lang/sys/Forms/MAI/AddRecipientsResult.aspx endpoint until the upgrade 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
    Locate MailEnable installation directory, typically found in C:\Program Files\MailEnable or C:\Program Files (x86)\MailEnable. Check for the presence of MailEnable binaries and configuration files.
    Affected if MailEnable is installed on the system
  2. Check MailEnable version
    Open MailEnable Administrator or check the version information of the MailEnable services. The version is typically displayed in the MailEnable Administrator console under Server status or in the Windows Programs and Features list.
    Affected if The installed version is prior to 10.54 (e.g., 10.53, 10.52, etc.)
  3. Verify vulnerable endpoint exists
    Check for the presence of AddRecipientsResult.aspx file in the path /Mondo/lang/sys/Forms/MAI/ within the MailEnable web directory. This file handles recipient addition operations.
    Affected if The AddRecipientsResult.aspx file exists in the expected location
  4. Test for reflected XSS vulnerability
    Send a crafted HTTP GET request to the AddRecipientsResult.aspx page with a malicious script in the 'Added' parameter, for example: GET /Mondo/lang/sys/Forms/MAI/AddRecipientsResult.aspx?Added=<script>alert(1)</script>. Inspect the HTTP response to see if the script is reflected without proper encoding.
    Affected if The 'Added' parameter value is reflected in the response without sanitization or encoding, allowing script injection

A user is affected if MailEnable version is below 10.54 AND the AddRecipientsResult.aspx endpoint is accessible AND the 'Added' GET parameter reflects unsanitized input in the HTTP 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, which contains the patch for this vulnerability. As a temporary workaround, disable or restrict access to the affected /Mondo/lang/sys/Forms/MAI/AddRecipientsResult.aspx endpoint until the upgrade can be applied.

Recommended fix High confidence

MailEnable 10.54

  1. Download MailEnable version 10.54 or later from the official MailEnable website (mailenable.com)
  2. Apply the update by running the installer or following the vendor's standard upgrade procedure
  3. Verify the fix by testing the affected endpoint /Mondo/lang/sys/Forms/MAI/AddRecipientsResult.aspx with a benign test payload in the 'Added' parameter to confirm proper sanitization

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

Fix this in Mailenable Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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