dbcve.org
MailenableApplication

CVE-2025-34420

HIGH · 7.8 CVSS v3.1 Published 2025-12-10
Fix available
A fix is available. Upgrade to 10.54 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 an unsafe DLL loading vulnerability that can lead to local arbitrary code execution. The MailEnable administrative executable attempts to load MEAIAM.DLL from its installation directory without sufficient integrity validation or a secure search order. A local attacker with write access to that directory can plant a malicious MEAIAM.DLL, which is then loaded on execution, resulting in attacker-controlled code running with the privileges of the process.

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 an unsafe DLL loading vulnerability where the administrative executable attempts to load MEAIAM.DLL from its installation directory without proper integrity checks or secure search order. A local attacker with write access to the installation directory can plant a malicious DLL that gets loaded upon execution, resulting in arbitrary code execution with the privileges of the admin process.

MitigationUpdate MailEnable to version 10.54 or later. Additionally, restrict filesystem write permissions on the MailEnable installation directory to prevent unauthorized DLL planting by non-privileged users.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 Windows Registry and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\MailEnable\InstallLevel or check the 'About' dialog in MailEnable Administrator console. Alternatively, check the file version of MEAdmin.exe in the installation directory.
    Affected if The installed version is lower than 10.54 (e.g., 10.53, 10.52, earlier versions).
  2. Locate MailEnable installation directory
    Check the default path C:\Program Files\MailEnable or look at the registry key HKEY_LOCAL_MACHINE\SOFTWARE\MailEnable\MailEnable's 'Install Directory' value.
    Affected if The installation directory is found and contains MailEnable executables.
  3. Verify MEAIAM.DLL presence
    Check if MEAIAM.DLL exists in the MailEnable installation directory using File Explorer or command: dir "C:\Program Files\MailEnable\MEAIAM.DLL"
    Affected if The file MEAIAM.DLL exists in the installation directory, meaning the vulnerable DLL loading attempt could occur.
  4. Inspect directory permissions
    Right-click the MailEnable installation folder, go to Properties > Security, and review which users and groups have Write or Modify permissions. Use icacls command: icacls "C:\Program Files\MailEnable"
    Affected if Non-administrative users or groups (such as Users, IIS_IUSRS, or authenticated users) have Write or Modify permissions on the installation directory, allowing DLL planting.

A user is affected if MailEnable version is below 10.54 AND non-privileged accounts have write access to the MailEnable installation directory where MEAIAM.DLL gets loaded.

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

Update MailEnable to version 10.54 or later. Additionally, restrict filesystem write permissions on the MailEnable installation directory to prevent unauthorized DLL planting by non-privileged users.

Recommended fix High confidence

10.54

  1. Backup the current MailEnable installation, configuration, and data directories before proceeding with the upgrade
  2. Stop all MailEnable services (MailEnable Service Manager or via Windows Services)
  3. Download MailEnable version 10.54 or later from the official MailEnable download page at mailenable.com
  4. Run the MailEnable upgrade installer with administrator privileges
  5. Follow the on-screen installation prompts to complete the upgrade
  6. Restart all MailEnable services after the upgrade completes
  7. Verify that the administrative interface loads correctly and the version shows 10.54 or later
  8. Confirm that MEAIAM.DLL is loaded from the correct system directory and not from a user-writable location
Caveat Review MailEnable release notes for 10.54 for any configuration or feature changes before upgrading in production environments

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