Skip to content

CWE-640: Weak Password Recovery Mechanism for Forgotten Password

BaseLikelihood of exploit: High

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

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 attacker tries to recover their password in a rapid succession. The system may send the original password to the user rather than generating a new temporary password. In summary, password recovery functionality, if not carefully designed and implemented can often become the system's weakest link that can be misused in a way that would allow an attacker to gain unauthorized access to the system.

Consequences

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

How to prevent it

  • 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.
  • Architecture and Design: Never allow the user to control what e-mail address the new password will be sent to in the password recovery mechanism.
  • Architecture and Design: Assign a new temporary password rather than revealing the original password.

Recent advisories

  • GHSA-x3vp-85cm-q97r — Microsoft Security Advisory CVE-2026-70175 - ASP.NET Core Elevation of Privilege Vulnerability
  • GHSA-4gv3-mc9p-5wqc — Keycloak: Unauthenticated account takeover via reset-credentials flow bypass
  • GHSA-8342-988q-86cr — n8n: Account Takeover via Unverified Email Claim in Token Exchange Embed Login
  • GHSA-m492-gv72-xvxj — Kimai Password Reset Link Remains Valid After Password Change
  • GHSA-w9xh-5f39-vq89 — phpMyFAQ: Missing Password Reset Token Allows Account Takeover via Username/Email Enumeration
  • GHSA-9qv9-8xv6-5p35 — phpMyFAQ: Unauthenticated Password Reset Endpoint Allows User Enumeration and Forced Password Change Without Token Validation
  • GHSA-gf43-24g3-5hw2 — Apostrophe has a Weak Password Recovery Mechanism for Forgotten Password and Improper Input Validation
  • GHSA-hp5w-3hxx-vmwf — Payload: Pre-Authentication Account Takeover via Parameter Injection in Password Recovery
  • GHSA-6wcw-r64p-qrrw — Cloudfoundry UAA has logic error in the token revocation endpoint implementation
  • GHSA-rfjg-6m84-crj2 — Vikunja Vulnerable to Account Takeover via Password Reset Token Reuse
  • GHSA-jxq9-79vj-rgvw — Statamic is vulnerable to account takeover via password reset link injection
  • GHSA-fmr2-m7gc-577w — funadmin has Weak Password Recovery Mechanism for Forgotten Password
  • GHSA-2w46-vq8h-98vh — Shopware 6's password recovery link does not expire after email change
  • GO-2025-4084 — ZITADEL Vulnerable to Account Takeover via Malicious Forwarded Header Injection
  • GHSA-cq42-vhv7-xr7p — Keycloak Denial of Service via account lockout

All advisories for CWE-640

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor