MailEnable Standard
CVE-2025-34418
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain local low-priv access to host
-
DeliveryWrite malicious MEAIMF.DLL into install directory
-
ExploitAdmin executable loads planted DLL
-
ExecutionAttacker code runs with process privileges
-
ImpactEscalate or persist on mail server
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 the attacker to already have LOCAL write access to the MailEnable installation directory in order to plant a malicious MEAIMF.DLL, and requires the MailEnable administrative executable to subsequently be started (typically by an administrator) so the planted DLL is loaded. Limiting factors: no remote network vector (AV:L), low privileges are still required (PR:L - the attacker must be able to write to that directory, which on a hardened install should be restricted to administrators), and the affected product is MailEnable Standard prior to version 10.54. These conditions make exploitation most realistic as a privilege-escalation or persistence step after an attacker has already obtained a foothold, rather than an initial-access vector. |
| Impact | This is a locally-exploitable DLL search-order hijacking flaw (CWE-427) rated CVSS 4.0 8.5 (High) by the reporter (VulnCheck). The provided CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H) confirms the attack requires LOCAL access and LOW privileges (PR:L) - it is not remotely exploitable, which meaningfully caps real-world urgency despite the high numeric score. Supporting signals reinforce lower priority: EPSS is only 0.17% (6th percentile), the CVE is NOT on CISA KEV, and no public exploit (POC) is identified in the provided data - so there is no public exploit identified at time of analysis. The high VC/VI/VA:H impact reflects full code execution with the process's privileges once the precondition (write access to the install directory) is met, but that precondition is itself a significant barrier on a correctly-secured host. Net assessment: this is a high-CVSS but comparatively low real-world-risk issue - a privilege-escalation/persistence primitive relevant to post-compromise or insider scenarios rather than a mass-exploitation threat. The AV:L vector and description are consistent (both indicate local access); no conflicting signals were found. |
| Exploit ScenarioDerived | A local attacker (or malware already running with limited privileges) who has write access to the MailEnable installation directory drops a malicious MEAIMF.DLL into that folder. When an administrator or service subsequently launches the MailEnable administrative executable, the planted DLL is loaded due to the insecure search order, running attacker code with that process's privileges. No public POC is referenced in the provided data, and the CVSS vector confirms local access with low privileges is required. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Local privilege escalation and code execution in MailEnable Standard prior to version 10.54, where the MailEnable administrative executable loads MEAIMF.DLL from its own installation directory without a secure search order or integrity validation (CWE-427, unsafe DLL loading). An attacker who already holds local write access to that directory can plant a malicious MEAIMF.DLL that executes with the privileges of the admin executable the next time it is started - typically by an administrator, making this a practical escalation or persistence step after an initial foothold rather than a remote entry vector. The flaw is rated CVSS 4.0 8.5 (High) by the reporter (VulnCheck), with our independent assessment at CVSS 3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H; EPSS is low at 0.17% (6th percentile), and no public exploit code has been identified at time of analysis, with no confirmed active exploitation (no CISA KEV listing).
RemediationAI
Vendor-released patch: upgrade MailEnable Standard to version 10.54 or later - the affected range is explicitly 'prior to 10.54' - and confirm the change against the release notes at https://mailenable.com/Standard-ReleaseNotes.txt and the advisory at https://www.vulncheck.com/advisories/mailenable-dll-hijacking-via-unsafe-loading-of-meaimf-dll. If immediate upgrade is not possible, apply compensating controls targeting the prerequisite rather than the code path: harden the NTFS ACLs on the MailEnable installation directory so that write/modify permissions are granted only to Administrators and SYSTEM, remove inherited permissions from unprivileged groups, and audit for any unexpected MEAIMF.DLL or other unsigned DLLs sitting in that directory (the trade-off is that overly restrictive ACLs can break MailEnable services, Webmail, or future upgrades if the service accounts and installers lose access, so test the ACLs against the MailEnable service account before enforcing them). Because exploitation requires local write access and an admin-initiated launch, restricting interactive logon and write paths on mail server hosts meaningfully reduces exposure, and monitoring process creation for the MailEnable administrative executable while also monitoring for newly written DLLs to the install directory provides detection coverage; no remote blocking rule is applicable since the vector is strictly local (AV:L).
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
The issue is a classic untrusted search path / DLL search-order hijacking flaw (CWE-427) affecting MailEnable Standard, the free edition of the MailEnable mail server for Windows (CPE cpe:2.3:a:mailenable:mailenable:*:*:*:*:standard:*:*:*). Rather than resolving the MEAIMF.DLL dependency through a hardened mechanism - such as loading by absolute path, validating the module's signature/hash, or restricting the DLL search to trusted system directories - the administrative executable binds the library from its own installation directory. On Windows, when an application directory is searched before or ahead of trusted locations and the directory is writable by non-administrative users, an attacker can pre-place a file with the expected name and have it resolved and executed in-process. The impact class here is local arbitrary code execution with the privileges of the loading executable; because the administrative console is commonly launched by an administrator, the loaded DLL can inherit those higher privileges, turning a low-privileged local write into high-integrity code execution.
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 write access to the install directory (AV:L, PR:L); once the executable runs the DLL executes automatically (UI:N, AC:L) yielding full C/I/A impact within the unchanged process scope.
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 MEAIMF.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 MEAIMF.DLL, which is then loaded when the executable starts, resulting in execution of attacker-controlled code with the privileges of the process.
Executive ViewAI
MailEnable Standard installations running versions below 10.54 contain an unsafe DLL-loading flaw in the administrative executable that lets a user who already has write access to the product's installation folder escalate to the privileges of the administrator who next launches that tool. The practical consequence is limited to environments where an attacker has already obtained a foothold on the mail server and can write into a directory that should be administrator-only, making this primarily a privilege-escalation and persistence risk rather than a direct external entry point. Leadership should care because mail servers are high-value, internet-facing assets, and a successful escalation here could yield full control of the messaging platform and the mailbox data it holds.
No vendor-released patch identified at time of analysis (the advisory describes affected versions as prior to 10.54, which should be confirmed and applied with the vendor as soon as it is generally available). Interim mitigations: restrict write and modify permissions on the MailEnable installation directory to Administrators and SYSTEM only, audit and validate the integrity of MEAIMF.DLL against a known-good copy, deploy file-integrity or EDR monitoring for DLL creation or modification in that path, apply application control or DLL search-order hardening, and enforce least privilege so that no non-administrative account holds directory write rights.
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 versions prior to 10.54, where the administrative executable loads MEAIAM.D
Local arbitrary code execution in MailEnable Standard editions prior to 10.54, where the MailEnable administrative execu
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB