Weak Passwords
Weak and default credentials are among the most exploited authentication vulnerabilities in web applications and network services.
These payloads are for authorized testing only — systems you own, authorized bug bounty programs, or controlled lab environments. Unauthorized testing is illegal.
What it is
Weak passwords and default credentials represent one of the most prevalent authentication vulnerabilities. Applications, devices, and services often ship with default credentials or accept trivially guessable passwords. Attackers use credential stuffing, password spraying, and brute-force attacks to compromise accounts using these common passwords.
Attack Vectors
- Admin panels (WordPress, Joomla, phpMyAdmin)
- Network devices (routers, switches, IoT)
- Database services (MySQL, MongoDB)
- Default application accounts
- Accounts where users choose weak passwords
Testing Methodology
- Test common default credentials for identified platforms
- Attempt password spraying with top-100 common passwords
- Check admin panel URLs (/admin, /wp-admin, /administrator)
- Test for password policy enforcement with weak inputs
Payloads
Reference payloads for authorized testing. Always verify you have permission before use.
Indicators of Vulnerability
- Successful login with default or common credentials
- Absence of account lockout after repeated failed attempts
- No minimum password length or complexity enforcement
Detection Guidance
Use breach database APIs to check if submitted passwords are in known breach lists. Implement password strength meters. Alert on logins with common credential patterns.
Mitigation & Remediation
- Enforce minimum password length (12+ characters)
- Check new passwords against known breached password databases
- Implement account lockout or exponential backoff after failed attempts
- Force password change on first login for default-credential accounts
- Require MFA for all accounts
References
Responsible Use
All content in this reference is for authorized security testing only. Use only on systems you own or have explicit written permission to test.
- Systems and applications you own
- Authorized penetration testing engagements
- Bug bounty programs with defined scope
- Educational lab environments (DVWA, WebGoat, HackTheBox)