dbcve.org
MailenableApplication

CVE-2025-34407

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 theme parameter of /Mondo/lang/sys/Forms/Statistics.aspx. The theme value is insufficiently sanitized when processed via a GET request and is reflected in the response, allowing an attacker to break out of an existing iframe context and inject arbitrary script. A remote attacker can supply a crafted payload that closes the iframe tag, 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 theme parameter of /Mondo/lang/sys/Forms/Statistics.aspx. The theme value from a GET request is insufficiently sanitized and reflected in the response, allowing an attacker to break out of an iframe context and inject arbitrary JavaScript by closing the iframe tag, inserting malicious script, and commenting out remaining code.

MitigationUpgrade to MailEnable version 10.54 or later which contains the security fix. Alternatively, implement proper input validation and output encoding on the theme parameter to sanitize user-supplied values before reflecting them in the response.

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. Check MailEnable version
    Open MailEnable Administrator, navigate to the About or General section, or check the Windows registry key: HKEY_LOCAL_MACHINE\SOFTWARE\MailEnable\Admin
    Affected if The installed version is lower than 10.54
  2. Verify Statistics.aspx is accessible
    Attempt to access https://yourserver/Mondo/lang/sys/Forms/Statistics.aspx or http://yourserver/Mondo/lang/sys/Forms/Statistics.aspx in a browser or via curl
    Affected if The page returns HTTP 200 and the Statistics.aspx endpoint exists and responds
  3. Test theme parameter for XSS reflection
    Send a GET request to /Mondo/lang/sys/Forms/Statistics.aspx?theme=testpayload and inspect the response HTML to see if the theme value is reflected without encoding (look for the raw value appearing in the response)
    Affected if The theme parameter value is reflected in the response HTML without proper HTML encoding or sanitization
  4. Check for iframe context vulnerability
    Send a crafted request such as /Mondo/lang/sys/Forms/Statistics.aspx?theme=%3C/iframe%3E%3Cscript%3Ealert(1)%3C/script%3E and verify if the script tag executes or appears unescaped in the response
    Affected if The response contains unescaped HTML tags from the theme parameter, allowing script injection
  5. Confirm external exposure
    Review firewall rules, IIS bindings, or reverse proxy configurations to determine if the /Mondo/ path is reachable from external networks
    Affected if The Statistics.aspx page is reachable from untrusted networks without authentication

A user is affected if MailEnable version is below 10.54 AND the Statistics.aspx page is accessible AND the theme parameter reflects input without sanitization.

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 security fix. Alternatively, implement proper input validation and output encoding on the theme parameter to sanitize user-supplied values before reflecting them in the response.

Recommended fix High confidence

10.54

  1. 1. Download MailEnable version 10.54 from the official MailEnable website (mailenable.com).
  2. 2. Backup your current MailEnable configuration and data before upgrading.
  3. 3. Install or upgrade to MailEnable version 10.54.
  4. 4. Verify the installation completed successfully.
  5. 5. Test the /Mondo/lang/sys/Forms/Statistics.aspx endpoint to confirm the theme parameter is now properly sanitized.

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-34407 — 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-34407 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