Cyber Resilience

CWE · MITRE source

CWE-1392Use of Default Credentials

Abstraction: Base · CVEs in our corpus: 104

The product uses default credentials (such as passwords or cryptographic keys) for potentially critical functionality.

It is common practice for products to be designed to use default keys, passwords, or other mechanisms 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, it is easier for attackers to bypass authentication quickly across multiple organizations.

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 · 7 mapping(s) from 3 framework(s): ATT&CK 5 (full) · OWASP-Web 1 (full) · ASVS 5.0 1 (mostly)

See the full cumulative-coverage rollup →

OWASP Top 10 for Web (2025)

This weakness contributes to A07:2025 Authentication Failures.

NIST 800-53 r5 controls that address this weakness (8)AI

Showing the 7 most specific. Generic controls that address many weakness types are collapsed below.

Control Title Family Why it addresses this CWE
IA-1Policy and ProceduresIAPolicy requires changing or avoiding default credentials during system setup and operation.
IA-2Identification and Authentication (Organizational Users)IAUnique identification requirement prevents use of default or shared credentials by organizational users.
IA-5Authenticator ManagementIAChanging default authenticators prior to first use prevents use of default credentials.
SA-4Acquisition ProcessSASecurity functional requirements and acceptance criteria can stipulate that acquired systems must not use default credentials.
SA-5System DocumentationSADocumentation of known configuration vulnerabilities and secure setup practices reduces reliance on default credentials.
CM-1Policy and ProceduresCMMandates replacement of default credentials during secure configuration and provisioning procedures.
PM-30Supply Chain Risk Management StrategyPMConsistent implementation of the strategy drives removal or mitigation of default credentials in procured systems and services.
Show 1 more broadly-applicable controls
IA-7Cryptographic Module AuthenticationIAStandards-compliant authentication mechanisms typically prohibit default credentials for cryptographic modules.

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-2024-128568.07.20.82192024-12-27
CVE-2023-306037.09.80.00852023-06-02
CVE-2023-37037.010.00.00522023-09-03
CVE-2023-308017.09.80.00912023-10-10
CVE-2023-496217.09.80.00602024-01-09
CVE-2024-298447.09.80.00632024-04-15
CVE-2024-77467.09.80.00532024-08-13
CVE-2024-122867.09.80.00422024-12-10
CVE-2025-301397.09.80.00392025-03-18
CVE-2025-29629 UPD7.09.10.00472025-07-25
CVE-2025-51536 UPD7.09.80.00502025-08-04
CVE-2025-51535 UPD7.09.10.00422025-08-04
CVE-2025-8731 UPD7.09.80.00592025-08-08
CVE-2025-354527.09.80.00792025-09-05
CVE-2025-550517.010.00.00322025-09-09
CVE-2025-350427.09.80.00402025-09-22
CVE-2025-105427.09.80.00672025-09-25
CVE-2025-345167.09.80.00532025-10-16
CVE-2025-122177.09.10.00272025-10-25
CVE-2025-122187.09.10.00272025-10-25
CVE-2025-543037.09.80.00342025-12-04
CVE-2022-508037.09.80.00362025-12-30
CVE-2026-263667.09.80.00652026-02-15
CVE-2026-263417.09.80.02662026-02-24
CVE-2026-277517.09.80.00452026-02-27