MailEnable
CVE-2025-34420
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain local write access to MailEnable install directory
-
ExploitPlant malicious MEAIAM.DLL in that directory
-
ExecutionAdministrative executable loads DLL via insecure search order
-
ImpactArbitrary code executes with process privileges
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V13 - Configuration Search path element control
|
| Exploitation Conditions | Exploitation requires LOCAL access to the Windows host and, critically, write permission to the MailEnable installation directory so the attacker can plant a malicious MEAIAM.DLL that the administrative executable loads due to an insecure DLL search order and missing integrity validation. It further requires that the MailEnable administrative executable is subsequently run (by an operator or the service) to trigger the load. Limiting factors: this is not remotely reachable (AV:L), it depends on the install directory being writable by the attacker (which secure default ACLs on a protected program directory would normally prevent), and resulting privileges are bounded by the privileges of the process that loads the DLL. Affected only on versions prior to 10.54. |
| Impact | This is a CWE-427 DLL hijacking / unsafe library loading flaw in MailEnable prior to 10.54. The vendor-supplied CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H, score 8.5) is internally consistent with the description: exploitation is LOCAL (AV:L), requires some existing privilege (PR:L) - specifically write access to the MailEnable installation directory - and yields full confidentiality, integrity, and availability impact once the planted MEAIAM.DLL is loaded. These signals agree with each other, but they describe a post-access privilege/persistence primitive, not a remotely reachable RCE. The real-world exploitation signals are weak: EPSS is only 0.17% (6th percentile), there is no CISA KEV listing, and no public exploit code is referenced - so this is no public exploit identified at time of analysis. Net assessment: despite the 'HIGH/8.5' headline, the LOCAL attack vector plus the precondition of pre-existing write access to a protected program directory make this a lower real-world priority than a network RCE of comparable score. It matters most as a local privilege-escalation / code-execution-as-the-mail-service vector where an attacker (or a low-privileged service account) can already write to the install path. Note the 'RCE' tag overstates the reachability: the CVSS explicitly marks this local (AV:L), so it is local arbitrary code execution, not remote. |
| Exploit ScenarioDerived | A low-privileged user or a compromised account on a Windows host running MailEnable (where the installation directory is writable, e.g. loose ACLs or non-default install location) drops a malicious MEAIAM.DLL into the MailEnable program folder. When an administrator or the service next runs the MailEnable administrative executable, the planted DLL is loaded due to the insecure search order, executing attacker code with that process's privileges. No public proof-of-concept is referenced for this specific CVE. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Local arbitrary code execution in MailEnable versions prior to 10.54, where the administrative executable loads MEAIAM.DLL from its installation directory without integrity validation or a secure search order, letting an attacker who can already write to that directory plant a malicious DLL that runs with the privileges of the MailEnable process. Exploitation requires local access and low privileges (CVSS PR:L) plus a subsequent execution of the affected executable, and is not remotely reachable or user-interactive; EPSS is 0.17% (6th percentile), no public exploit was identified at time of analysis, and there is no CISA KEV listing. Impact is high for confidentiality, integrity and availability within the loading process's privilege context, but is bounded by those privileges and by whether default directory ACLs actually permit an attacker to write there.
RemediationAI
Upgrade to MailEnable 10.54 or later: the affected range is explicitly everything prior to 10.54, and the vendor's release notes (https://mailenable.com/Standard-ReleaseNotes.txt) list that build as the first outside it, so treat 10.54 as the minimum fixed version and confirm the matching build for any non-Standard edition before rollout. If the upgrade cannot be applied immediately, the decisive compensating control is to harden the MailEnable installation directory with NTFS ACLs so that only Administrators and SYSTEM hold write/modify rights while the service account is limited to read and execute; this removes the attacker's ability to drop a rogue MEAIAM.DLL, but it will break any in-place updater or third-party plugin that writes into that path, so perform updates through an elevated maintenance window instead. Note that generic DLL-hijack countermeasures such as enabling SafeDllSearchMode or stripping the current directory from the search order do not help here, because the DLL is loaded from the application's own directory, which the Windows loader always consults first; the same limitation applies to path-based workarounds. Supplemental measures with detection rather than prevention value include monitoring for unexpected or unsigned MEAIAM.DLL files in the MailEnable install tree and application allow-listing that blocks unsigned DLL loads by the administrative process, and the full technical detail is in the VulnCheck advisory at https://www.vulncheck.com/advisories/mailenable-dll-hijacking-via-unsafe-loading-of-meaiam-dll.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This is a CWE-427 uncontrolled search path element (DLL hijacking / unsafe library loading) issue in the MailEnable mail server for Windows. The administrative executable resolves MEAIAM.DLL by name and loads it from its own installation directory without validating the binary's integrity (for example via Authenticode/signature checks) and without constraining resolution with the modern Windows loader APIs such as SetDefaultDllDirectories or LOAD_LIBRARY_SEARCH_APPLICATION_DIR/SYSTEM32. Because the application directory is searched first for DLLs loaded by name, any file named MEAIAM.DLL placed there is executed in-process when the administrative tool runs, inheriting that process's token - typically an elevated administrator or service context. The attack is a post-compromise primitive: it presupposes local write access to a directory that secure default ACLs would normally reserve for Administrators and SYSTEM, and it requires the affected executable to be launched afterwards. The supplied CPE, cpe:2.3:a:mailenable:mailenable:*:*:*:*:standard:*:*:*, pins the affected package to the MailEnable Standard edition across all builds before 10.54; the CVSS vector AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N (and the assessor's CVSS 3.1 equivalent AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) confirms there is no remote or unauthenticated attack surface and no scope change beyond the vulnerable process.
Know when Mailenable gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Local DLL planting requires existing write access to the install directory so AV:L and PR:L; execution is reliable (AC:L) with no user interaction and full C/I/A impact in the process context.
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
DescriptionCVE.org
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.
Executive ViewAI
MailEnable versions prior to 10.54 are affected by a local DLL hijacking vulnerability that could allow an authenticated attacker with low privileges to execute arbitrary code in the context of the MailEnable service. With no public exploit identified at time of analysis and exploitation requiring local access, the immediate risk is limited, but successful compromise could impact email confidentiality, integrity, and availability. Leadership should prioritize verifying that only trusted administrators can write to the MailEnable installation directory and monitor for suspicious activity, as this flaw could be used in post-exploitation scenarios.
No vendor patch available; restrict write access to the MailEnable installation directory to authorized administrators only, implement application whitelisting, and monitor for unauthorized DLL placement.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Affected Products (CPE)CVE.org
More in Mailenable
View allXSS in MailEnable before v10 via failure.aspx. EPSS 11.5%. PoC available.
Cross-site scripting (XSS) vulnerability in ForgottenPassword.aspx in MailEnable Professional, Enterprise, and Premium 4
MailEnable Enterprise Premium 10.23 was vulnerable to XML External Entity Injection (XXE) attacks that could be exploite
MailEnable versions prior to 10.55 contain a reflected cross-site scripting (XSS) vulnerability in the webmail interface
MailEnable versions prior to 10.55 contain a reflected cross-site scripting (XS) vulnerability in the webmail interface
MailEnable versions prior to 10.55 contain a reflected cross-site scripting (XSS) vulnerability in the webmail interface
MailEnable Enterprise Premium 10.23 did not use appropriate access control checks in a number of areas. Rated high sever
Privilege escalation via authorization bypass in MailEnable Enterprise Premium 10.55 and earlier lets a low-privileged W
Local DLL hijacking in MailEnable (mail server for Windows) lets an attacker who can write to the installation directory
DLL hijacking in MailEnable Standard versions prior to 10.54 allows local attackers with write access to the installatio
Local arbitrary code execution in MailEnable Standard editions prior to 10.54, where the MailEnable administrative execu
Local DLL hijacking in MailEnable versions prior to 10.54 allows an attacker who can already write to the product's inst
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB