Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.
Use of Default Credentials
This vulnerability occurs when a system, device, or application relies on pre-configured, publicly known credentials like passwords or encryption keys for access to critical functions.
What is CWE-1392?
Real-world CVEs caused by CWE-1392
-
Remote Terminal Unit (RTU) uses default credentials for some SSH accounts
-
data visualization/sharing package uses default secret keys or cookie values if they are not specified in environment variables
-
microcontroller board has default password
-
cloud cluster management product has a default master encryption key
-
Intrusion Detection System (IDS) uses the same static, private SSL keys for multiple devices and installations, allowing decryption of SSL traffic
Step-by-step attacker path
- 1
Identify a code path that handles untrusted input without validation.
- 2
Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.
- 3
Deliver the payload through a normal request and observe the application's reaction.
- 4
Iterate until the response leaks data, executes attacker code, or escalates privileges.
Vulnerable pseudo
MITRE has not published a code example for this CWE. The pattern below is illustrative — see Resources for canonical references.
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
// Untrusted input flows directly into the sensitive sink.
return executeUnsafe(input);
} Secure pseudo
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
const safe = validateAndEscape(input);
return executeWithGuards(safe);
} How to prevent CWE-1392
- Requirements Prohibit use of default, hard-coded, or other values that do not vary for each installation of the product - especially for separate organizations.
- Architecture and Design Force the administrator to change the credential upon installation.
- Installation / Operation The product administrator could change the defaults upon installation or during operation.
How to detect CWE-1392
Run dynamic application security testing against the live endpoint.
Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.
Code review: flag any new code that handles input from this surface without using the validated framework helpers.
Plexicus auto-detects CWE-1392 and opens a fix PR in under 60 seconds.
Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.
Frequently asked questions
What is CWE-1392?
This vulnerability occurs when a system, device, or application relies on pre-configured, publicly known credentials like passwords or encryption keys for access to critical functions.
How serious is CWE-1392?
MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.
What languages or platforms are affected by CWE-1392?
MITRE lists the following affected platforms: Not OS-Specific, Not Architecture-Specific, ICS/OT, Not Technology-Specific.
How can I prevent CWE-1392?
Prohibit use of default, hard-coded, or other values that do not vary for each installation of the product - especially for separate organizations. Force the administrator to change the credential upon installation.
How does Plexicus detect and fix CWE-1392?
Plexicus's SAST engine matches the data-flow signature for CWE-1392 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.
Where can I learn more about CWE-1392?
MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/1392.html. You can also reference OWASP and NIST documentation for adjacent guidance.
Weaknesses related to CWE-1392
Use of Weak Credentials
This vulnerability occurs when a system relies on weak authentication credentials—like default passwords, hard-coded keys, or easily…
Weak Password Requirements
This vulnerability occurs when an application fails to enforce strong password policies, making user accounts easier to compromise through…
Use of Hard-coded Credentials
This vulnerability occurs when software contains built-in, unchangeable authentication secrets like passwords or encryption keys within…
Use of Default Password
This vulnerability occurs when a system or device uses a pre-configured, publicly known password for authentication, often for…
Use of Default Cryptographic Key
This vulnerability occurs when a system uses a pre-configured, publicly known cryptographic key for security-critical operations instead…
Don't Let Security
Weigh You Down.
Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.