dbcve.org
MailenableApplication

CVE-2025-34397

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 Message parameter of /Mobile/Compose.aspx. The Message value is not properly sanitized when processed via a GET request and is reflected into a JavaScript context in the response. By supplying a crafted payload that terminates the existing script block/function, injects attacker-controlled JavaScript, and comments out the remaining code, a remote attacker can execute arbitrary JavaScript in a victim’s browser when the victim opens the crafted reply URL. 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 before 10.54 contain a reflected XSS vulnerability in /Mobile/Compose.aspx where the Message GET parameter is not sanitized before being reflected into a JavaScript context in the response. An attacker can craft a payload that terminates the existing script block, injects malicious JavaScript, and comments out remaining code to execute arbitrary scripts in victim browsers.

MitigationUpgrade to MailEnable version 10.54 or later, which contains the patch for this vulnerability. Until then, implement input validation on the Message parameter and ensure proper output encoding when reflecting user input into JavaScript contexts.

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. Identify MailEnable installation and version
    Check the MailEnable installation directory for version information. Common locations: C:\Program Files\MailEnable\BIN\MEPM.exe -v, or check the Windows Programs and Features list, or look at the assembly version of DLLs in the MailEnable bin folder.
    Affected if The installed version is below 10.54.
  2. Confirm Mobile web interface is accessible
    Verify that the /Mobile/ virtual directory or application exists under the MailEnable web mail path. Check IIS Manager or the file system at the MailEnable web mail root for a Mobile folder containing Compose.aspx.
    Affected if The /Mobile/Compose.aspx file exists and is accessible via the web server.
  3. Test the Message parameter for reflected XSS
    Send a GET request to /Mobile/Compose.aspx with a test payload in the Message parameter, such as: /Mobile/Compose.aspx?Message=<script>alert(1)</script>. Examine the response HTML to see if the parameter value is reflected without proper encoding or sanitization.
    Affected if The Message parameter value is reflected unescaped into the HTML/JavaScript response, allowing script injection.

A user is affected if they are running any version of MailEnable below 10.54 AND have the Mobile web interface enabled, with the Message parameter reflecting unsanitized input into the 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. Until then, implement input validation on the Message parameter and ensure proper output encoding when reflecting user input into JavaScript contexts.

Recommended fix High confidence

10.54

  1. Obtain MailEnable version 10.54 from the official MailEnable website (mailenable.com) or authorized distribution channels
  2. Back up the current MailEnable configuration, database, and any custom settings
  3. Stop MailEnable services before applying the upgrade
  4. Install MailEnable version 10.54 using the standard upgrade installation process
  5. Restart MailEnable services after the upgrade completes
  6. Verify the version has been updated to 10.54 or later
  7. Test that the /Mobile/Compose.aspx endpoint properly sanitizes the Message parameter and no longer reflects unsanitized input

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

Fix this in Mailenable Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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