Loading vulnerability…
CVE-2025-43919 describes an alleged arbitrary file read issue in GNU Mailman 2.1.39 as bundled in cPanel and WHM. The claim is that an unauthenticated attacker can exploit a ../ directory traversal condition at the /mailman/private/mailman endpoint, identified as the private archive authentication endpoint, by supplying a crafted username parameter. If valid, the flaw would allow traversal outside the intended path and access to arbitrary files readable by the Mailman/web application context. However, the available content also notes that multiple third parties reported being unable to reproduce the issue, regardless of whether cPanel or WHM was used. Specific vulnerable code paths or functions are not provided in the supplied material.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository provides a proof-of-concept (PoC) exploit for CVE-2025-43919, a directory traversal vulnerability in GNU Mailman 2.1.39 as bundled with cPanel/WHM. The exploit is implemented in a single Python script (cve_2024_43919_poc.py), which sends a crafted POST request to the vulnerable /mailman/private/mailman CGI endpoint. By manipulating the 'username' parameter to include directory traversal sequences, an unauthenticated attacker can read arbitrary files from the server, such as /etc/passwd, Mailman configuration files, or mailbox archives. The repository also includes a README.md with detailed vulnerability information, exploitation scenarios, mitigation advice, and example usage. The exploit does not provide a shell or code execution, but enables sensitive file disclosure, which could be chained with other vulnerabilities for further impact. The code is straightforward, requires only the target URL and file path as arguments, and is suitable for demonstrating the vulnerability in a test or assessment context.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.