MailEnable CVE-2025-34416

Requires local write access to the MailEnable installation directory so the attacker can plant a malicious MEAIPO.DLL, and requires the MailEnable administrative executable to be started (typically by an administrator or service) after the DLL is planted, at which point it is loaded via an insecure search order without integrity validation. Limiting factors: exploitation is local only (not remote), the attacker must already possess filesystem write permission to a privileged application's install directory, and the payload executes with the privileges of the launching process rather than guaranteeing elevation beyond that. Affected only on MailEnable versions prior to 10.54; upgrading remediates it.

This is a local privilege-dependent DLL hijacking flaw (CWE-427), not a remote entry point. The provided CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N) confirms it requires local access and some existing privilege - specifically write access to the MailEnable installation directory - to plant a malicious MEAIPO.DLL. Impact is high across confidentiality, integrity, and availability (VC:H/VI:H/VA:H) because the planted DLL executes with the privileges of the administrative executable's process. However, exploitation signals are weak: EPSS is only 0.17% (6th percentile), there is no CISA KEV listing, and no public exploit code is referenced, indicating no evidence of real-world exploitation. The local attack vector plus a precondition of directory write access substantially limit practical risk - an attacker who can already write to the install directory often has significant foothold already. This is best characterized as a defense-in-depth / local-escalation issue rather than a widespread-exploitation priority; its 8.5 CVSS 4.0 score overstates urgency relative to its low exploitation probability and local-only reach. No data directly conflicts, but note the score is the vendor/reporter CVSS 4.0 and no independent 3.1 score was provided.

A local attacker (or a lower-privileged service/user) with write access to the MailEnable installation directory drops a malicious MEAIPO.DLL into that folder. When an administrator or the MailEnable administrative process subsequently launches the executable, the planted DLL is loaded due to an insecure search order and lack of integrity validation, executing attacker-controlled code with the process's privileges. No public exploit code was identified at the time of analysis.