How to fix: Default credentials may be in use
Vendor default usernames or passwords detected in configuration or source.
Why it matters
Default credentials (admin/admin, root/root, admin/password) are the first thing attackers try. They are published in vendor documentation and widely known, making any system using them trivially compromised.
Software shipped with default credentials must have them changed before first exposure to any network.
How to fix it
- 1Change all default credentials immediately on installation
- 2Disable default admin accounts and create named service accounts
- 3Add credential-change verification to your deployment checklist
Code examples
Change default credentials on first deployment
# Change default admin credentials immediately on install
# For databases:
psql -U postgres -c "ALTER USER postgres PASSWORD 'new_strong_password';"
# For services: disable default users and create named service accounts
# Never deploy with vendor default passwords
# Use a password manager or secrets manager for all credentialsReferences
Detected automatically by VulnRadar. The check id is default-credentials, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is Default credentials may be in use?
- VulnRadar rates this high severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id default-credentials, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Default credentials may be in use map to?
- It maps to CWE-1392. In the OWASP Top 10 it falls under A07:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.