CWE · MITRE source
CWE-523Unprotected Transport of Credentials
Login pages do not use adequate measures to protect the user name and password while they are in transit from the client to the server.
Last updated: 04 July 2026 00:28 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 · 5 mapping(s) from 4 framework(s): STIG rhel 8 2 (mostly) · OWASP-Web 1 (full) · ATT&CK 1 (mostly) · CAPEC 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A04:2025 Cryptographic Failures.
NIST 800-53 r5 controls that address this weakness (3)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-37 | Out-of-band Channels | SC | Using a distinct channel for credential transmission prevents unprotected transport over the application's normal communication path. |
SC-8 | Transmission Confidentiality and Integrity | SC | Requiring protected transport for credentials directly mitigates unprotected credential transmission over networks. |
SC-9 | Transmission Confidentiality | SC | Prevents unprotected transport of credentials by mandating confidentiality mechanisms such as TLS for all sensitive data flows. |
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). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2020-25175 | 7.0 | 9.8 | 0.0114 | 2020-12-14 |
CVE-2024-1509 | 7.0 | 9.1 | 0.0034 | 2025-02-28 |
CVE-2017-16731 | 5.5 | 8.8 | 0.0072 | 2017-12-20 |
CVE-2021-32003 | 5.5 | 8.0 | 0.0023 | 2021-08-05 |
CVE-2021-38460 | 5.5 | 7.5 | 0.0170 | 2021-10-12 |
CVE-2022-31805 | 5.5 | 7.5 | 0.0095 | 2022-06-24 |
CVE-2023-31277 | 5.5 | 7.5 | 0.0046 | 2023-07-06 |
CVE-2025-57800 UPD | 5.5 | 8.8 | 0.0043 | 2025-08-22 |
CVE-2025-61121 | 5.5 | 7.5 | 0.0027 | 2025-10-30 |
CVE-2025-64309 UPD | 5.5 | 7.4 | 0.0018 | 2025-11-15 |
CVE-2025-66029 | 5.5 | 7.6 | 0.0017 | 2025-12-17 |
CVE-2025-61916 | 5.5 | 7.9 | 0.0015 | 2026-01-05 |
CVE-2023-28708 | 3.5 | 4.3 | 0.0183 | 2023-03-22 |
CVE-2023-22862 | 3.5 | 5.9 | 0.0054 | 2023-06-05 |
CVE-2024-1102 | 3.5 | 6.5 | 0.0079 | 2024-04-25 |
CVE-2024-20395 | 3.5 | 6.4 | 0.0022 | 2024-07-17 |
CVE-2025-41705 | 3.5 | 6.8 | 0.0042 | 2025-10-14 |
CVE-2025-64308 UPD | 3.5 | 6.5 | 0.0022 | 2025-11-15 |
CVE-2026-23635 | 3.5 | 6.5 | 0.0032 | 2026-03-25 |
CVE-2026-8673 UPD | 3.5 | 5.9 | 0.0019 | 2026-05-22 |
CVE-2026-36610 UPD | 3.5 | 5.9 | 0.0015 | 2026-06-03 |