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: 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: mostly · 3 mapping(s) from 2 framework(s): ATT&CK 2 (mostly) · OWASP-Web 1 (mostly)
OWASP Top 10 for Web (2025)
This weakness contributes to A07:2025 Authentication Failures.
NIST 800-53 r5 controls that address this weakness (3)AI
| 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. |
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-2023-45249 KEV | 10.0 | 9.8 | 0.5353 | 2024-07-24 |
CVE-2022-4126 | 7.0 | 9.6 | 0.0062 | 2023-03-27 |
CVE-2023-25131 | 7.0 | 9.4 | 0.0097 | 2023-04-24 |
CVE-2023-32090 | 7.0 | 9.8 | 0.0052 | 2023-08-07 |
CVE-2023-24049 | 7.0 | 9.8 | 0.0073 | 2023-12-04 |
CVE-2024-29666 UPD | 7.0 | 9.8 | 0.0074 | 2024-03-25 |
CVE-2024-29021 | 7.0 | 9.0 | 0.2018 | 2024-04-18 |
CVE-2024-30802 | 7.0 | 9.8 | 0.0052 | 2024-05-14 |
CVE-2024-50588 | 7.0 | 9.8 | 0.0068 | 2024-11-08 |
CVE-2024-51555 | 7.0 | 10.0 | 0.0041 | 2024-12-05 |
CVE-2025-26701 | 7.0 | 10.0 | 0.0044 | 2025-03-11 |
CVE-2025-22938 | 7.0 | 9.8 | 0.0052 | 2025-03-31 |
CVE-2025-27690 | 7.0 | 9.8 | 0.0045 | 2025-04-10 |
CVE-2025-8077 | 7.0 | 9.8 | 0.0052 | 2025-09-17 |
CVE-2025-66050 | 7.0 | 9.8 | 0.0033 | 2026-01-09 |
CVE-2026-24429 | 7.0 | 9.8 | 0.0037 | 2026-01-26 |
CVE-2026-22886 | 7.0 | 9.8 | 0.0040 | 2026-03-03 |
CVE-2026-4404 | 7.0 | 9.4 | 0.0050 | 2026-03-23 |
CVE-2026-33784 | 7.0 | 9.8 | 0.0046 | 2026-04-09 |
CVE-2026-35075 UPD | 7.0 | 9.8 | 0.0047 | 2026-06-03 |
CVE-2023-28094 | 5.5 | 8.1 | 0.0053 | 2023-06-22 |
CVE-2023-43042 | 5.5 | 7.5 | 0.0072 | 2023-12-14 |
CVE-2024-43659 | 5.5 | 7.2 | 0.0083 | 2025-01-09 |
CVE-2024-49559 | 5.5 | 8.8 | 0.0045 | 2025-03-17 |
CVE-2024-13966 UPD | 5.5 | 7.3 | 0.0032 | 2025-05-27 |