Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2021 - Vulnerable and Outdated Components
ASVS 5.0
V6 - Authentication Response uniformity
|
| Impact | CVSS 8.6 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L) indicates a highly accessible vulnerability requiring no authentication, low complexity, and high confidentiality impact. However, real-world risk depends on several factors: (1) Active exploitation status and KEV listing would significantly elevate priority; (2) Existence of proof-of-concept code indicates operational threat; (3) EPSS score, if available, would quantify exploitation probability relative to other CVEs; (4) The vulnerability is pre-authentication and network-accessible, meeting SSVC criteria for 'exploitable' with high likelihood; (5) Technical impact includes information disclosure (valid device enumeration) which could support lateral reconnaissance. The confidentiality impact (C:H) is the primary concern—attackers can discover valid devices for follow-on attacks. The limited integrity/availability impact (I:L/A:L) suggests this is primarily a reconnaissance vector. Organizations managing networked devices should prioritize patching, but exploit complexity is LOW, making this a credible threat if devices are internet-exposed. |
| Exploit ScenarioDerived | An attacker conducting reconnaissance on internet-exposed devices performs the following attack: (1) Identifies target organization's IP ranges hosting web-managed devices; (2) Initiates unauthenticated HTTP/HTTPS requests to management interface login endpoints with username payloads: '0000000000', '0000000001', '0000000002'... (3) Observes response differences—valid usernames may return 'invalid password' while invalid usernames return 'user not found' or differ in response timing; (4) Efficiently enumerates valid device identifiers across the organization's network; (5) Uses discovered device identifiers for targeted attacks: password guessing, phishing with accurate device numbers, social engineering IT staff ('Your device 5834729102 has a critical issue...'), or reconnaissance before physical attacks. If automation is available, enumeration of 1 billion device IDs is computationally achievable in hours/days depending on rate limits. No authentication required; AV:N and AC:L mean this occurs purely through network reconnaissance. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 14, 2026
User enumeration vulnerability affecting web management interfaces where usernames are limited to device identifiers (10-digit numerical values). An unauthenticated remote attacker can enumerate valid user accounts by systematically testing digit sequences, potentially gaining information disclosure and limited system manipulation capabilities. The CVSS 8.6 rating reflects high confidentiality impact, though patch status and active exploitation details require vendor-specific assessment.
RemediationAI
Immediate remediation steps: (1) Contact vendor for patches addressing enumeration protection; (2) Apply vendor-supplied firmware updates when available—specifics depend on device manufacturer; (3) Interim mitigations: restrict management interface access via firewall rules limiting source IP ranges, implement WAF/IDS rules detecting sequential authentication attempts, enforce rate limiting on login endpoints, implement account lockout after failed attempts; (4) Administrative controls: disable default/predictable device identifiers where possible, require strong supplementary authentication (MFA), monitor authentication logs for enumeration patterns; (5) Architectural: network segmentation isolating management interfaces to trusted administrative networks. Vendors should implement enumeration defenses: constant-time username validation, progressive delays, CAPTCHAs, and consider randomized or longer usernames.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This vulnerability is rooted in CWE-204 (Observable Discrepancy / Information Exposure Through Discrepancy), where the authentication mechanism exhibits detectable differences between valid and invalid usernames. The underlying issue stems from poor username entropy combined with weak or absent enumeration protection mechanisms (rate limiting, account lockout delays, response time analysis resistance). Devices using sequential or predictable numerical identifiers as sole authentication credentials create a trivial enumeration surface. The web management interface likely lacks protections such as: constant-time response comparisons, progressive delays on failed attempts, CAPTCHA challenges, or account lockout policies. This is compounded by the 10-digit maximum constraint (~1 billion possible values), making brute-force enumeration computationally feasible.
Know when Brute Force gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
DescriptionCVE.org
User names used to access the web management interface are limited to the device identifier, which is a numerical identifier no more than 10 digits. A malicious actor can enumerate potential targets by incrementing or decrementing from known identifiers or through enumerating random digit sequences.
Executive ViewAI
CVE-2025-5485 exposes web management interfaces to user enumeration attacks due to predictable device identifier-based usernames, allowing attackers to systematically discover and target your managed devices. Organizations operating these devices face unauthorized access attempts and potential compromise of critical management functions without immediate patching options.
Implement IP-based access controls restricting management interface to trusted networks; enable account lockout policies after failed login attempts; deploy WAF rules to throttle authentication requests and block sequential enumeration patterns; disable remote management access if feasible; enforce multi-factor authentication if supported; monitor authentication logs for enumeration attempts using device identifier sequences.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Brute Force
View allRuggedCom Rugged Operating System (ROS) before 3.3 has a factory account with a password derived from the MAC Address fi
An issue in the password change function of Silverpeas v6.4.2 and lower allows for the bypassing of password complexity
Victure RX1800 EN_V1.0.0_r12_110933 was discovered to utilize a weak default password which includes the last 8 digits o
Critical authentication bypass vulnerability in OpenC3 COSMOS v6.0.0 caused by weak password requirements that enable br
QaTraq 6.9.2 ships with administrative account credentials which are enabled in default installations and permit immedia
I-doit pro 25 and below and I-doit open 25 and below employ weak password requirements for Administrator account creatio
Weak Password Requirements in GitHub repository modoboa/modoboa prior to 2.1.0. Rated critical severity (CVSS 9.8), this
Weak Password Requirements in GitHub repository janeczku/calibre-web prior to 0.6.20. Rated critical severity (CVSS 9.8)
Weak Password Requirements in GitHub repository thorsten/phpmyfaq prior to 3.1.12. Rated critical severity (CVSS 9.8), t
Beijing Zed-3 Technologies Co.,Ltd VoIP simpliclty ASG 8.5.0.17807 (20181130-16:12) has a Weak password vulnerability. R
Weak Password Requirements in GitHub repository thorsten/phpmyfaq prior to 3.1.8. Rated critical severity (CVSS 9.8), th
Weak Password Requirements in GitHub repository ikus060/minarca prior to 4.2.2. Rated critical severity (CVSS 9.8), this
EUVD-2025-18211
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB