CWE · MITRE source
CWE-836Use of Password Hash Instead of Password for Authentication
The product records password hashes in a data store, receives a hash of a password from a client, and compares the supplied hash to the hash obtained from the data store.
Some authentication mechanisms rely on the client to generate the hash for a password, possibly to reduce load on the server or avoid sending the password across the network. However, when the client is used to generate the hash, an attacker can bypass the authentication by obtaining a copy of the hash, e.g. by using SQL injection to compromise a database of authentication credentials, or by exploiting an information exposure. The attacker could then use a modified client to replay the stolen hash without having knowledge of the original password. As a result, the server-side comparison against a client-side hash does not provide any more security than the use of passwords without hashing.
Last updated: 14 October 2026 20:41 UTC
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls PROPOSED for this weakness (0)AI-assisted
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 |
|---|---|---|---|
| No NIST controls proposed yet. | |||
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2023-34132 UPD | 8.1 | 9.8 | 0.0768 | 2023-07-13 |
CVE-2021-23857 UPD | 7.6 | 10.0 | 0.0123 | 2021-10-04 |
CVE-2017-7927 UPD | 7.4 | 7.3 | 0.3675 | 2017-05-06 |
CVE-2022-32282 UPD | 6.9 | 8.8 | 0.0181 | 2022-08-22 |
CVE-2023-23614 UPD | 6.7 | 8.8 | 0.0097 | 2023-01-26 |
CVE-2023-39546 UPD | 6.6 | 8.8 | 0.0063 | 2023-11-17 |
CVE-2023-4299 UPD | 6.4 | 9.0 | 0.0068 | 2023-08-31 |
CVE-2026-9222 UPD | 6.1 | 8.1 | 0.0041 | 2026-06-26 |
CVE-2025-62618 UPD | 6.0 | 8.0 | 0.0032 | 2025-10-31 |
CVE-2025-52543 UPD | 5.8 | 7.5 | 0.0031 | 2025-09-02 |
CVE-2019-25552 UPD | 5.8 | 7.5 | 0.0040 | 2026-03-21 |
CVE-2026-63158 | 5.7 | 7.4 | 0.0041 | 2026-10-13 |
CVE-2026-44736 | 5.1 | 6.5 | 0.0039 | 2026-06-26 |
CVE-2023-23450 UPD | 5.0 | 6.2 | 0.0071 | 2023-05-15 |
CVE-2025-64471 UPD | 3.9 | 4.9 | 0.0034 | 2025-12-09 |
CVE-2026-40103 UPD | 3.7 | 4.3 | 0.0035 | 2026-04-10 |
CVE-2025-48925 UPD | 3.6 | 4.3 | 0.0026 | 2025-05-28 |