A simple way to lock down login security for multisite and regular WordPress installations.
Blocks brute force and dictionary attacks without inconveniencing legitimate users or administrators
- Tracks IP addresses, usernames, and passwords
- Monitors logins made by form submissions and auth cookies
- If a login failure uses data matching a past failure, the plugin slows down response times. The more failures, the longer the delay. This limits attackers ability to effectively probe your site, so they'll give up and go find an easier target.
- If an account seems breached, the "user" is immediately logged out and forced to use WordPress' password reset utility. This prevents any damage from being done and verifies the user's identity. But if the user is coming in from an IP address they have used in the past, an email is sent to the user making sure it was them logging in. All without intervention by an administrator.
- Can notify the administrator of attacks and breaches
- Supports IPv6
Thoroughly examines and enforces password strength. Includes full UTF-8 character set support if PHP's
mbstringextension is enabled. The tests have caught every password dictionary entry I've tried.
- Minimum length (customizable)
- Doesn't match blog info
- Doesn't match user data
- Must either have numbers, punctuation, upper and lower case characters or be very long. Note: alphabets with only one case (e.g. Arabic, Hebrew, etc.) are automatically exempted from the upper/lower case requirement.
- Non-sequential codepoints
- Non-sequential keystrokes (custom sequence files can be added)
- Not in the password dictionary files you've provided (if any)
- Decodes "leet" speak
- The password/phrase is not found by the
dictdictionary program (if available)
Password aging (optional) (not recommended)
- Users need to change password every x days (customizable)
- Grace period for picking a new password (customizable)
- Remembers old passwords (quantity is customizable)
Administrators can require all users to change their passwords
- Done via a flag in each user's database entry
- No mail is sent, keeping your server off of spam lists
Logs out idle sessions (optional) (idle time is customizable)
Maintenance mode (optional)
- Publicly viewable content remains visible
- Disables logins by all users, except administrators
- Logs out existing sessions, except administrators
- Disables posting of comments
- Useful for maintenance or emergency reasons
- This is separate from WordPress' maintenance mode
Prevents information disclosures from failed logins
Improvements Over Similar WordPress Plugins
- Multisite network support
- Monitors authentication cookies for bad user names and hashes
- Adjusts WordPress' password policy user interfaces
- Takes security seriously so the plugin itself does not open your site to SQL, HTML, or header injection vulnerabilities
- Notice-free code means no information disclosures if
display_errorsis on and
- Only loads files, actions, and filters needed for enabled options and the page's context
- Provides an option to have deactivation remove all of this plugin's data from the database
- Uses WordPress' features rather than fighting or overriding them
- No advertising, promotions, or beacons
- Proper internationalization support
- Clean, documented code
- Unit tests covering 100% of the main class
- Internationalized unit tests
For reference, the similar plugins include:
- Better WP Security
- Limit Login Attempts
- Login Lock
- Login LockDown
- PMC Lockdown
- Simple Login Lockdown
Compatibility with Other Plugins
Some plugins provide similar functionality. These overlaps can lead to conflicts during program execution. Please read the FAQ!
- Franais, franais (French, France) (fr_FR) by mermouy
- Portugus, Brasil (Portugese, Brazil) (pt_BR) by Valdir Trombini
Why Strong, Unique Passwords Are Important
Yeah, creating, storing/remembering, and using a different, strong password for each site you use is a hassle. But it is absolutely necessary.
Password lists get stolen on a regular basis from big name sites (like Linkedin for example!). Criminals then have unlimited time to decode the passwords. In general, 50% of those passwords are so weak they get figured out in a matter of seconds. Plus there are computers on the Internet dedicated to pounding the sites with login attempts, hoping to get lucky.
Many people use the same password for multiple sites. Once an attacker figures out your password on one site, they'll try it on your accounts at other sites. It gets ugly very fast.
But don't despair! There are good, free tools that make doing the right thing a piece of cake. For example: KeePassX, KeePass, or 1Password
Securing Your WordPress Site is Important
You're probably thinking "There's nothing valuable on my website. No one will bother breaking into it." What you need to realize is that attackers are going after your visitors. They put stealth code on your website that pushes malware into your readers' browsers.
According to SophosLabs more than 30,000 websites are infected every day and 80% of those infected sites are legitimate. Eighty-five percent of all malware, including viruses, worms, spyware, adware and Trojans, comes from the web. Today, drive-by downloads have become the top web threat.
-- Security Threat Report 2012
So if your site does get cracked, not only do you waste hours cleaning up, your reputation gets sullied, security software flags your site as dangerous, and worst of all, you've inadvertently helped infect the computers of your clients and friends. Oh, and if the attack involves malware, that malware has probably gotten itself into your computer.
|Version||Release Date||Change Log|
(2012-09-17) = * Translate "Confirm" and "No thanks" phrases on the settings screen. * Adjust readme to indicate that development has moved to GitHub.
* Adjust formatting of the
(2012-09-15) = * Remove loophole: slow down successful logins as well (for non-verified IP addresses). Keeps attackers from using timeouts to skip our delayed responses to failed login attempts. * Reduce false positives for breach notifications and password resets: - Allow users through without incident if the user's Network IP failure count is less than the "Breach Email Confirm" setting. The old behavior was to do so only if the Network IP failure count was 0. - Add user's current IP to their verified IP list whenever they save their profile page, not just when they change their password. - Fix when user notifications are sent. Do so if the IP address is NOT verified instead of if the IP address IS verified. Duh. - Don't notify administrators of a successful login if the user is coming in from a verified IP address. - Change subject line of user notification emails to differentiate them from emails sent to admins. - Reword user notification email and have it explain how to reduce future hassles. * Remove URIs from user notification email to avoid phishing imitations. * Add pt_BR translation. Thanks to Valdir Trombini. * Put plugin version number in admin notification emails. * Update the fr_FR translation: update password policy, add settings page. * Put Unicode flag on the two preg calls that didn't have it. Fixes password parsing problem on Windows. * Add date to log() messages. * Unit tests pass using PHP 5.4.5-dev, 5.3.16-dev, and 5.2.18-dev. * Tested under WordPress 3.4.2 using regular and multisite. * Also tested on Windows 7 using PHP 5.4.5 and WordPress 3.4.1.