CWE · MITRE source
CWE-640Weak Password Recovery Mechanism for Forgotten Password
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.
Last updated: 19 November 2026 23:37 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: full · 31 mapping(s) from 5 framework(s): ATT&CK 17 (full) · ISO_IEC_27002_2022 7 (mostly) · 4 (mostly) · 800-53 2 (mostly) · ASVS 5.0 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A07:2025 Authentication Failures.
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls PROPOSED for this weakness (1)
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
IA-5 | Authenticator Management | IA | graded mostly Establishing procedures for lost or compromised authenticators addresses weak password recovery mechanisms. |
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2019-18818 UPD | 9.9 | 9.8 | 0.9748 | 2019-11-07 |
CVE-2023-7028 KEV UPD | 9.9 | 10.0 | 0.9446 | 2024-01-12 |
CVE-2019-19844 UPD | 9.4 | 9.8 | 0.5356 | 2019-12-18 |
CVE-2025-6216 UPD | 9.3 | 9.8 | 0.4742 | 2025-06-21 |
CVE-2017-7615 UPD | 9.2 | 8.8 | 0.9120 | 2017-04-16 |
CVE-2024-2862 UPD | 8.9 | 9.1 | 0.5100 | 2024-03-25 |
CVE-2025-47646 UPD | 8.7 | 9.8 | 0.2472 | 2025-05-23 |
CVE-2017-17097 UPD | 8.0 | 9.8 | 0.0695 | 2018-01-02 |
CVE-2018-19488 UPD | 7.9 | 9.8 | 0.0416 | 2019-03-21 |
CVE-2012-5686 UPD | 7.9 | 9.8 | 0.0476 | 2020-02-04 |
CVE-2026-19632 | 7.9 | 9.8 | 0.0450 | 2026-08-26 |
CVE-2018-12421 UPD | 7.8 | 9.8 | 0.0272 | 2018-06-14 |
CVE-2018-7811 UPD | 7.8 | 9.8 | 0.0350 | 2018-11-30 |
CVE-2026-12571 UPD | 7.8 | 9.8 | 0.0327 | 2026-08-11 |
CVE-2015-4689 UPD | 7.7 | 9.8 | 0.0228 | 2017-09-11 |
CVE-2018-7809 UPD | 7.7 | 9.8 | 0.0247 | 2018-11-30 |
CVE-2019-11393 UPD | 7.7 | 9.8 | 0.0209 | 2019-04-22 |
CVE-2021-22763 UPD | 7.7 | 9.8 | 0.0190 | 2021-06-11 |
CVE-2026-18963 UPD | 7.7 | 9.1 | 0.0809 | 2026-08-18 |
CVE-2017-2766 UPD | 7.6 | 9.8 | 0.0163 | 2017-02-03 |
CVE-2017-7551 UPD | 7.6 | 9.8 | 0.0142 | 2017-08-16 |
CVE-2018-10081 UPD | 7.6 | 9.8 | 0.0153 | 2018-04-13 |
CVE-2018-1000501 UPD | 7.6 | 9.8 | 0.0156 | 2018-06-26 |
CVE-2018-17298 UPD | 7.6 | 9.8 | 0.0176 | 2018-09-21 |
CVE-2018-17881 UPD | 7.6 | 9.8 | 0.0150 | 2018-10-03 |