Default Wordlist Configuration
Wordlist paths are configured insource/config.py:
Wordlist Types
- Password Wordlist
- Directory Wordlist
Used by WPScan for WordPress login brute-force attacks (menu option 5)
- Size: 139.9 MB (compressed), 14,344,391 passwords
- Source: Real passwords from RockYou data breach (2009)
- Format: Plain text, one password per line
- Coverage: Includes common passwords, leetspeak, keyboard patterns
Verifying Wordlist Availability
Before running audits, verify wordlists exist:Custom Wordlist Setup
Creating Custom Password Wordlists
For targeted attacks, create custom wordlists:- Top Passwords Only
- Organization-Specific
- Generate with Crunch
Create subset of rockyou.txt:Update config.py:Benefits:
- Faster brute-force (seconds vs hours)
- Good for testing/development
- Covers most common weak passwords
Creating Custom Directory Wordlists
Optimize directory enumeration with targeted wordlists:- SecLists
- Custom Paths
- Filtered DIRB
Install SecLists collection:Update config.py:
Performance Considerations
Wordlist Size vs Speed
Wordlist Size vs Speed
Impact on attack duration:
*Approximate times, varies by network speed and target responsivenessRecommendations:
| Wordlist | Size | WPScan Time* | Gobuster Time* |
|---|---|---|---|
| top1000.txt | 1,000 | ~30 seconds | ~5 seconds |
| top10k.txt | 10,000 | ~5 minutes | ~30 seconds |
| common.txt | 4,614 | ~2 minutes | ~20 seconds |
| rockyou.txt | 14M | ~8-12 hours | N/A |
| directory-list-2.3-medium.txt | 220K | N/A | ~10 minutes |
- Development/Testing: Use top1000-10000 for quick results
- CTF/Labs: Use full rockyou.txt for comprehensive coverage
- Production Pentests: Start small, escalate if needed
Network and Target Impact
Network and Target Impact
Factors affecting performance:
- Network Latency:
- Local VM: <1ms (fast)
- Same subnet: 1-10ms (moderate)
- Remote host: 50-200ms (slow)
- Target Response Time:
- Failed login: 50-100ms
- Rate limiting: 1-5 seconds per attempt
- WAF/IPS: May block after N attempts
- Concurrent Threads:
- WPScan: 5-10 threads (default)
- Gobuster: 10 threads (default)
- Higher threads = faster but more detectable
Optimization Strategies
Optimization Strategies
1. Start Small, Escalate:2. Filter by Intelligence:3. Combine with OSINT:
Common Wordlist Locations
Standard wordlist paths across distributions:Troubleshooting
Wordlist Not Found Error
Wordlist Not Found Error
Error:Solutions:
Permission Denied Error
Permission Denied Error
Error:Solutions:
Attack Too Slow
Attack Too Slow
Problem: WPScan taking hours with rockyou.txtSolutions:
Best Practices
Development
- Use small wordlists (1K-10K entries)
- Fast feedback loop for testing
- Verify functionality before full run
Production Pentests
- Start with common passwords
- Escalate to full wordlists if needed
- Monitor for rate limiting/blocking
CTF Challenges
- Use full rockyou.txt for coverage
- Check for password hints in challenge
- Create custom wordlists from hints
Lab Practice
- Test different wordlist sizes
- Measure performance impact
- Experiment with custom wordlists
Related Documentation
Configuration Settings
View all configuration options including COMMON_PASSWORDS
WordPress Attack
Learn how WPScan uses the password wordlist
Directory Enumeration
See how Gobuster uses directory wordlists
Hash Cracking
Understand the two-phase cracking process