CVE-2025-34419
BaseFortify
Publication date: 2025-12-10
Last updated on: 2025-12-10
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| mailenable | mailenable | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-427 | The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in MailEnable versions prior to 10.54 where the administrative executable loads a DLL named MEAISM.DLL from its installation directory without proper integrity checks or secure search order. A local attacker who has write access to that directory can place a malicious MEAISM.DLL file, which will be loaded by the executable, allowing the attacker to execute arbitrary code with the privileges of the process.
How can this vulnerability impact me? :
The vulnerability can lead to local arbitrary code execution by an attacker with write access to the installation directory. This means an attacker could run malicious code with the same privileges as the MailEnable administrative process, potentially compromising the system or gaining elevated access.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by checking if your MailEnable installation directory contains a suspicious or unexpected MEAISM.DLL file that could be malicious. Additionally, verify the version of MailEnable installed to see if it is prior to 10.54. Commands to assist detection include: 1) Checking the MailEnable version, e.g., using the MailEnable administrative interface or querying the installed software version. 2) Listing the DLL files in the MailEnable installation directory to identify any unauthorized MEAISM.DLL files, for example, using 'dir' on Windows Command Prompt or 'Get-ChildItem' in PowerShell. 3) Monitoring process loads or using tools like Process Monitor to detect if MEAISM.DLL is being loaded from an unexpected location.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Upgrade MailEnable to version 10.54 or later where the vulnerability is fixed. 2) Restrict write permissions on the MailEnable installation directory to prevent unauthorized users from placing malicious DLLs. 3) Monitor and audit the installation directory for any unexpected DLL files, especially MEAISM.DLL. 4) Avoid running the MailEnable administrative executable with elevated privileges unless necessary.