CWE-640: Weak Password Recovery Mechanism for Forgotten Password

Description:
The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak.

Extended Description:
It is common for an application to have a mechanism that provides a means for a user to gain access to their account in the event they forget their password. Very often the password recovery mechanism is weak, which has the effect of making it more likely that it would be possible for a person other than the legitimate system user to gain access to that user's account. Weak password recovery schemes completely undermine a strong password authentication scheme. 
             This weakness may be that the security question is too easy to guess or find an answer to (e.g. because the question is too common, or the answers can be found using social media). Or there might be an implementation weakness in the password recovery mechanism code that may for instance trick the system into e-mailing the new password to an e-mail account other than that of the user. There might be no throttling done on the rate of password resets so that a legitimate user can be denied service by an attacker if an 

Affected languages: Not Language-Specific
Parent weaknesses: CWE-1390, CWE-287

Consequences:
  - Access Control: Gain Privileges or Assume Identity
  - Availability: DoS: Resource Consumption (Other)
  - Integrity: Other

Mitigations:
  - [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.
  - [Architecture and Design] Require that the user properly answers the security question prior to resetting their password and sending the new password to the e-mail address of record.

Demonstrative examples:
A famous example of this type of weakness being exploited is the eBay attack. eBay always displays the user id of the highest bidder. In the final minutes of the auction, one of the bidders could try to log in as the highest bidder three times. After three incorrect log in attempts, eBay password throttling would kick in and lock out the highest bidder's account for some time. An attacker could then make their own bid and their victim would not have a chance to place the counter bid because they would be locked out. Thus an attacker could win the auction.

Real-world examples:
  - CVE-2025-1570: password reset functionality for a WordPress plugin allows a brute force attack of the one-time password
  - CVE-2024-9302: password reset functionality for a WordPress plugin allows a brute force attack of the one-time password
  - CVE-2024-5277: password recovery mechanism for AI developer toolkit does not invalidate the reset password token after it is used, allowing attackers to reuse the token to change passwords of victims
  - CVE-2024-38287: web conference product resets passwords to random 8-digit values, allowing brute force attacks by retrieving the hash