{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-34421 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-34421 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-34421 is a high-severity vulnerability in Mailenable Mailenable, published on 10 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-34421 and fix it if it is affected.\n\nWhat it is: CVE-2025-34421 is a high-severity vulnerability in Mailenable Mailenable, published on 10 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-34421 in the wild and no public exploit code.\n\nAffected product: Mailenable Mailenable. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-34421/ (Markdown: https://insights.sbomify.com/CVE-2025-34421/index.md)","id":"CVE-2025-34421","markdown":"https://insights.sbomify.com/CVE-2025-34421/index.md","name":"CVE-2025-34421","record":{"aliases":["GHSA-g4vc-m5pm-qwxv"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Mail server software","requires_auth":"low_privilege","summary":"Local attackers can execute arbitrary code by planting a malicious DLL in the MailEnable installation directory, requiring an upgrade to mitigate.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"mailenable","vendor":"mailenable"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-427","name":"Uncontrolled Search Path Element"}],"description":"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 MEAISP.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 MEAISP.DLL, which is then loaded on execution, resulting in attacker-controlled code running with the privileges of the process.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"MailEnable \u003c 10.54 DLL Hijacking via Unsafe Loading of MEAISP.DLL","id":"CVE-2025-34421","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"mailenable:mailenable","products":["mailenable:mailenable"],"type":"other","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"MailEnable \u003c 10.54 DLL Hijacking via Unsafe Loading of MEAIPC.DLL","id":"CVE-2025-34422"},"packages":[],"prev":{"headline":"MailEnable \u003c 10.54 DLL Hijacking via Unsafe Loading of MEAIAM.DLL","id":"CVE-2025-34420"},"products":["MailEnable"],"published":"2025-12-10","related":[{"cvss_score":10,"headline":"XML external entity in n/a","id":"CVE-2015-9280","kev_date_added":null,"published":"2019-01-16"},{"cvss_score":9.8,"headline":"Cross-site scripting in n/a","id":"CVE-2025-44148","kev_date_added":null,"published":"2025-06-03"},{"cvss_score":9.8,"headline":"XML external entity in n/a","id":"CVE-2019-12924","kev_date_added":null,"published":"2019-07-08"},{"cvss_score":9.8,"headline":"MailEnable before 8.60 allows Privilege Escalation because admin accounts could be created as a consequence of %0A mishandling in AUTH.TAB a","id":"CVE-2015-9278","kev_date_added":null,"published":"2019-01-16"},{"cvss_score":9.1,"headline":"Path traversal in n/a","id":"CVE-2015-9277","kev_date_added":null,"published":"2019-01-16"},{"cvss_score":8.8,"headline":"Path traversal in n/a","id":"CVE-2022-42136","kev_date_added":null,"published":"2023-01-13"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2019-12926","kev_date_added":null,"published":"2019-07-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-14","vendors":["MailEnable"]},"summary":"Local attackers can execute arbitrary code by planting a malicious DLL in the MailEnable installation directory, requiring an upgrade to mitigate.","url":"https://insights.sbomify.com/CVE-2025-34421/"}