CVE-2024-44762 is an account enumeration vulnerability in Webmin Usermin v2.100. The issue arises because the application returns different error messages for invalid login attempts depending on whether the supplied username corresponds to a valid account. By observing these discrepancies during authentication failures, an attacker can distinguish existing usernames from nonexistent ones. Based on the provided information, the vulnerability is limited to information disclosure through the authentication interface; no specific vulnerable function or code path is identified in the supplied content.
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 (2 hidden).
This repository contains a single Python script (CVE-2024-44762.py) that exploits a username enumeration vulnerability in Usermin version 2.100. The script takes a target URL and a wordlist of usernames as input. For each username, it sends a POST request to the /password_change.cgi endpoint, attempting to change the password with a fake old password. By analyzing the error messages in the HTTP response, the script determines whether the username exists on the system. If the error message indicates that the password is incorrect (rather than the username not being found), the username is likely valid. The script is a proof-of-concept for CVE-2024-44762 and is intended for security testing and demonstration purposes. The only fingerprintable endpoint is the /password_change.cgi path on the Usermin web interface.
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.
3 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.