CWE · MITRE source
CWE-1393Use of Default Password
The product uses default passwords for potentially critical functionality.
It is common practice for products to be designed to use default passwords for authentication. The rationale is to simplify the manufacturing process or the system administrator's task of installation and deployment into an enterprise. However, if admins do not change the defaults, then it makes it easier for attackers to quickly bypass authentication across multiple organizations. There are many lists of default passwords and default-password scanning tools that are easily available from the World Wide Web.
Last updated: 20 August 2026 13:14 UTC
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 that address this weakness (3)AI-assisted
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
IA-5 | Authenticator Management | IA | Changing default authenticators prior to first use prevents use of default passwords. |
IA-7 | Cryptographic Module Authentication | IA | Requires authentication that meets guidelines, avoiding default passwords for cryptographic module access. |
PM-16 | Threat Awareness Program | PM | Threat awareness programs disseminate botnet and scanning activity tied to default passwords, driving organizations to change or enforce non-default credentials before mass exploitation occurs. |
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2023-45249 KEV UPD | 9.9 | 9.8 | 0.5325 | 2024-07-24 |
CVE-2024-29021 UPD | 7.6 | 9.0 | 0.2018 | 2024-04-18 |
CVE-2023-32090 UPD | 7.4 | 9.8 | 0.0062 | 2023-08-07 |
CVE-2023-24049 UPD | 7.4 | 9.8 | 0.0073 | 2023-12-04 |
CVE-2024-29666 UPD | 7.4 | 9.8 | 0.0074 | 2024-03-25 |
CVE-2024-50588 UPD | 7.4 | 9.8 | 0.0070 | 2024-11-08 |
CVE-2024-51555 UPD | 7.4 | 10.0 | 0.0041 | 2024-12-05 |
CVE-2025-26701 UPD | 7.4 | 10.0 | 0.0044 | 2025-03-11 |
CVE-2024-30802 UPD | 7.3 | 9.8 | 0.0052 | 2024-05-14 |
CVE-2025-22938 UPD | 7.3 | 9.8 | 0.0052 | 2025-03-31 |
CVE-2025-27690 UPD | 7.3 | 9.8 | 0.0047 | 2025-04-10 |
CVE-2025-8077 UPD | 7.3 | 9.8 | 0.0056 | 2025-09-17 |
CVE-2026-24429 | 7.3 | 9.8 | 0.0037 | 2026-01-26 |
CVE-2026-22886 UPD | 7.3 | 9.8 | 0.0040 | 2026-03-03 |
CVE-2026-33784 UPD | 7.3 | 9.8 | 0.0046 | 2026-04-09 |
CVE-2026-35075 UPD | 7.3 | 9.8 | 0.0047 | 2026-06-03 |
CVE-2023-25131 UPD | 7.2 | 9.4 | 0.0097 | 2023-04-24 |
CVE-2025-66050 | 7.2 | 9.8 | 0.0034 | 2026-01-09 |
CVE-2026-5269 | 7.2 | 9.8 | 0.0027 | 2026-07-14 |
CVE-2026-16504 | 7.2 | 9.8 | 0.0027 | 2026-07-31 |
CVE-2026-4404 UPD | 7.1 | 9.4 | 0.0049 | 2026-03-23 |
CVE-2022-4126 UPD | 6.8 | 9.6 | 0.0062 | 2023-03-27 |
CVE-2026-16503 | 6.7 | 9.1 | 0.0025 | 2026-07-31 |
CVE-2024-49559 UPD | 6.6 | 8.8 | 0.0046 | 2025-03-17 |
CVE-2025-2766 UPD | 6.5 | 8.8 | 0.0030 | 2025-06-06 |