VulnerabilityPublished 16 Oct 2024Updated 17 Oct 2024

CVE-2024-44762: Webmin Usermin · Generation of Error Message Containing Sensitive Information

Source CVE Database V5

Public exploit available (Exploit-DB) · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 2.5% chance of exploitation in 30 days – higher than 85% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 16 Oct 2024
Detectable: evidence found.
nuclei template: Usermin 2.100 - Username Enumeration
Weaponised: evidence found.
2 Exploit-DB entries, the first 169 days after disclosure
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by MITRE Corporation
21 Aug 2024, 56 days before disclosure
CVE published
on cve.org
16 Oct 2024, t = 0
First Exploit-DB entry (opens in a new tab)
Webmin Usermin 2.100 - Username Enumeration +1 more
3 Apr 2025, 169 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-44762, organizations should implement the following specific measures: 1) Restrict access to Webmin Usermin login interfaces using network-level controls such as VPNs, IP whitelisting, or firewall rules to limit exposure to trusted networks or users only. 2) Monitor and analyze login attempts for patterns indicative of username enumeration or brute force attacks, employing intrusion detection or prevention systems with tailored rules. 3) Enforce strong password policies and deploy multi-factor authentication (MFA) to reduce the risk of account compromise even if usernames are enumerated. 4) Regularly check for and apply security updates or patches from Webmin developers once available. 5) Consider customizing or hardening error messages to avoid revealing whether a username exists, thereby eliminating the information leakage vector. 6) Educate system administrators and users about the risks of phishing and social engineering that could leverage enumerated usernames. 7) Conduct periodic security assessments and penetration tests focusing on authentication mechanisms to identify similar weaknesses.

Description

A discrepancy in error messages for invalid login attempts in Webmin Usermin v2.100 allows attackers to enumerate valid user accounts.

Impact

The primary impact of CVE-2024-44762 is the disclosure of valid usernames through error message discrepancies during login attempts. This information leakage can significantly aid attackers in mounting targeted brute force attacks, credential stuffing, or phishing campaigns. While the vulnerability does not directly compromise system integrity or availability, the enumeration of valid accounts increases the attack surface and the likelihood of successful unauthorized access. Organizations using Webmin Usermin for server management may face increased risk of account compromise, especially if combined with weak password policies or lack of multi-factor authentication. The vulnerability could also facilitate lateral movement within networks if attackers gain valid credentials. Given the network-exploitable nature and no requirement for authentication, this flaw can be exploited remotely by attackers scanning for vulnerable systems. Although no active exploitation is reported yet, the potential for reconnaissance and subsequent attacks makes this vulnerability a concern for IT infrastructure security.

Exploit-DB

Nuclei detection templates

Usermin 2.100 - Username Enumerationmedium (opens in a new tab)

Public tooling indexed from Metasploit Framework, Exploit-DB and ProjectDiscovery nuclei-templates. Its existence raises the odds of exploitation; it does not confirm attacks.

CWE-209Generation of Error Message Containing Sensitive Information (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product generates an error message that includes sensitive information about its environment, users, or associated data.
Implementation
Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended).
Implementation
Handle exceptions internally and do not display errors containing potentially sensitive information to a user.
Implementation · Attack Surface Reduction
Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (opens in a new tab)
Padding Oracle Crypto Attack (opens in a new tab)
Query System for Information (opens in a new tab)
Blind SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

senscybersecurity.nl/cve-2024-44762-explained/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Description

AI analysisMachine-generated, updated 28 Feb 2026, 06:45 UTC

Public exploits and detection2 Exploit-DB entries, a Nuclei detection template

WeaknessesCWE-209

Technical details

References

Community reviews

Related threats