VulnerabilityPublished 2 Jan 2024Updated 3 Jun 2025

CVE-2024-0186: HuiRan Host Reseller System · Weak Password Recovery

Affects HuiRan Host Reseller SystemSource CVE Database V5

Not known to be exploited · CVSS 3.7 Low.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score

3.7Low

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

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

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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

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

Affected software

Product	Affected	Fixed in
HuiRan Host Reseller System	Affected =2.0	Fixed in–

AI-suggested

Given the absence of an official patch, European organizations should implement compensating controls to mitigate this vulnerability. These include: 1) Restricting access to the password recovery endpoint through network controls such as IP whitelisting or VPN access to reduce exposure. 2) Enhancing monitoring and logging of password recovery attempts to detect anomalous or repeated requests indicative of exploitation attempts. 3) Implementing multi-factor authentication (MFA) on accounts to reduce the impact of unauthorized password resets. 4) Reviewing and strengthening the password recovery process by adding additional verification steps, such as out-of-band confirmation or security questions, if possible. 5) Educating users about phishing and social engineering risks related to password recovery. 6) Planning for an upgrade or patch deployment once the vendor releases a fix. 7) Conducting regular security assessments of the hosting reseller system to identify and remediate other potential weaknesses.

Description

A vulnerability classified as problematic has been found in HuiRan Host Reseller System up to 2.0.0. Affected is an unknown function of the file /user/index/findpass?do=4 of the component HTTP POST Request Handler. The manipulation leads to weak password recovery. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-249444.

Impact

For European organizations using HuiRan Host Reseller System, this vulnerability poses a risk primarily to the integrity of user accounts managed through the system. Since the system is used for hosting reselling, unauthorized access could lead to manipulation of hosting accounts, potentially resulting in service disruptions or unauthorized changes to hosted content. Although the severity is low, the impact could be more significant if attackers leverage this weakness as a foothold for further attacks within the organization’s infrastructure. The remote exploitability without authentication increases the risk surface, especially for organizations with externally accessible password recovery endpoints. However, the high attack complexity and lack of known active exploitation reduce immediate risk. Organizations relying on this system should be aware that attackers might attempt to exploit this vulnerability to reset passwords or gain unauthorized access, which could indirectly affect service integrity and customer trust.

Summary

CVE-2024-0186 is a vulnerability identified in HuiRan Host Reseller System version 2.0.0 and earlier. The issue resides in the password recovery functionality accessed via the HTTP POST request handler at the endpoint /user/index/findpass?do=4. Specifically, the vulnerability is categorized under CWE-640, which refers to weak password recovery mechanisms. This weakness allows an attacker to potentially exploit the password recovery process to gain unauthorized access or manipulate account credentials. The vulnerability can be exploited remotely without requiring authentication or user interaction, but the attack complexity is considered high, and the exploitability is difficult. The CVSS v3.1 base score is 3.7, indicating a low severity primarily due to the high attack complexity and lack of direct confidentiality or availability impact. No known exploits are currently observed in the wild, and no patches have been published yet. The vulnerability disclosure date is January 2, 2024. The weakness in the password recovery process could allow an attacker to bypass intended security controls, potentially leading to limited integrity impact, such as unauthorized password resets or account takeovers, but without direct data confidentiality or system availability compromise.

CWE-640Weak Password Recovery Mechanism for Forgotten Password (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak.
Architecture and Design
Make sure that all input supplied by the user to the password recovery mechanism is thoroughly filtered and validated.
Architecture and Design
Do not use standard weak security questions and use several security questions.
Architecture and Design
Make sure that there is throttling on the number of incorrect answers to a security question. Disable the password recovery functionality after a certain (small) number of incorrect guesses.
OWASP Cheat Sheets
Choosing and Using Security Questions (opens in a new tab)
Forgot Password (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.5.3 (opens in a new tab)
V2.5.2 (opens in a new tab)
V2.5.1 (opens in a new tab)
Attack patterns
Password Recovery Exploitation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Jul 2025, 05:26 UTC

WeaknessesCWE-640

Technical details

References

Community reviews

Related threats