iThemes Security is the #1 WordPress Security Plugin
iThemes Security (formerly Better WP Security) gives you over 30+ ways to secure and protect your WordPress site. On average, 30,000 new websites are hacked each day. WordPress sites can be an easy target for attacks because of plugin vulnerabilities, weak passwords and obsolete software.
Most WordPress admins don’t know they’re vulnerable, but iThemes Security works to lock down WordPress, fix common holes, stop automated attacks and strengthen user credentials. With advanced features for experienced users, our WordPress security plugin can help harden WordPress.
Maintained and Supported by iThemes
iThemes has been building and supporting WordPress tools since 2008 like BackupBuddy, our WordPress backup plugin. With our full range of WordPress plugins, themes and training, WordPress security is the next step in providing you with everything you need to build the WordPress web.
Get Plugin Support and Pro Features
Get added peace of mind with professional support from our expert team and pro features to take your site’s security to the next level with iThemes Security Pro.
Расширенные возможности (PRO):
- Two-Factor Authentication — Use a mobile app such as Google Authenticator or Authy to generate a code or have a generated code emailed to you.
- WordPress Salts & Security Keys — The iThemes Security plugin makes updating your WordPress keys and salts easy.
- Malware Scan Scheduling — Have your site scanned for malware automatically each day. If an issue is found, an email is sent with the details.
- Защита паролем — Создание надежных паролей прямо из вашего профиля.
- Password Expiration — Set a maximum password age and force users to choose a new password. You can also force all users to choose a new password immediately (if needed).
- Google reCAPTCHA — Protect your site against spammers.
- User Action Logging — Track when users edit content, login or logout.
- Import/Export Settings — Saves time setting up multiple WordPress sites.
- Dashboard Widget — Manage important tasks such as user banning and system scans right from the WordPress dashboard.
- Online File Comparison — When a file change is detected it will scan the origin of the files to determine if the change was malicious or not. Currently works only in WordPress core but plugins and themes are coming.
- Temporary Privilege Escalation — give a contractor or someone else temporary admin or editor access to your site that will automatically reset itself.
- wp-cli Integration — Manage your site’s security from the command line.
iThemes Sync Integration
Manage more than one WordPress site? Manage Away Mode, release lockouts and keep your themes, plugins and WordPress core up to date from one dashboard with iThemes Sync. Start managing 10 WordPress sites for free with iThemes Sync.
iThemes Brute Force Attack Protection Network
iThemes Security takes brute force attack protection to the next level by banning users who have tried to break into other sites from breaking into yours. The iThemes Brute Force Attack Protection Network will automatically report IP addresses of failed login attempts and will block them for a length of time necessary to protect your site based on the number of sites that have seen a similar attack.
iThemes Security работает, чтобы защитить ваш сайт путем блокировки плохих пользователей и повышения безопасности паролей и другой важной информации.
- Prevents brute force attacks by banning hosts and users with too many invalid login attempts
- Scans your site to instantly report where vulnerabilities exist and fixes them in seconds
- Bans troublesome user agents, bots and other hosts
- Усиливает безопасность сервера
- Enforces strong passwords for all accounts of a configurable minimum role
- Forces SSL for admin pages (on supporting servers)
- Forces SSL for any page or post (on supporting servers)
- Turns off file editing from within WordPress admin area
- Detects and blocks numerous attacks to your filesystem and database
iThemes Security monitors your site and reports changes to the filesystem and database that might indicate a compromise. iThemes Security also works to detect bots and other attempts to search vulnerabilities.
- Detects bots and other attempts to search for vulnerabilities.
- Monitors filesystem for unauthorized changes.
- Run a scan for malware and blacklists on the homepage of your site.
- Receive email notifications when someone gets locked out after too many failed login attempts or when a file on your site has been changed.
iThemes Security hides common WordPress security vulnerabilities, preventing attackers from learning too much about your site and away from sensitive areas like your site’s login, admin, etc.
- Changes the URLs for WordPress dashboard areas including login, admin and more
- Completely turns off the ability to login for a given time period (away mode)
- Removes theme, plugin, and core update notifications from users who do not have permission to update them
- Removes Windows Live Write header information
- Removes RSD header information
- Renames «admin» account
- Changes the ID on the user with ID 1
- Changes the WordPress database table prefix
- Changes wp-content path
- Removes login error messages
iThemes Security makes regular backups of your WordPress database, allowing you to get back online quickly in the event of an attack. Use iThemes Security to create and email database backups on a customizable schedule.
For complete site backups and the ability to restore or move WordPress to a new host or domain, check out BackupBuddy.
Other WordPress Security Benefits
- Makes it easier for users not accustomed to WordPress to remember login and admin URLs by customizing default admin URLs
- Detects hidden 404 errors on your site that can affect your SEO such as bad links and missing images
WordPress Security Tutorials
Learn how to use our WordPress security plugin with our series of in-depth tutorial videos:
- Works on multi-site (network) and single site installations
- Works with Apache, LiteSpeed or NGINX (Note: NGINX will require you to manually edit your virtual host configuration)
- Features like database backups and file checks can be problematic on servers without a minimum of 64MB of RAM. All testing servers allocate 128MB to WordPress and usually don’t have any other plugins installed.
- Spanish by Andrew Kurtis
Please let us know if you would like to contribute a translation.
Please read the installation instructions and FAQ before installing this WordPress security plugin. iThemes Security makes significant changes to your database and other site files which can be problematic, so a backup is strongly recommended before making any changes to your site with this plugin. While problems are rare, most support requests involve the failure to make a proper backup before installation.
Released under the terms of the GNU General Public License.
- Почему iThemes Security требует последнюю версию WordPress? Можно мне использовать немного более старую версию?
- One of the best security practices for a WordPress site owner is keeping software up to date. Because of this, we only test this plugin on the latest stable version of WordPress and will only guarantee it works in the latest version.
- Предотвратит ли плагин все атаки на мой сайт?
- No. iThemes Security is designed to help improve the security of your WordPress installation from many common attack methods, but it cannot prevent every possible attack. Nothing replaces diligence and good practice. This plugin makes it a little easier for you to apply both.
- Этот плагин для новой установки WordPress или можно использовать на существующих сайтах?
- Many of the changes made by this plugin are complex and can break existing sites. While iThemes Security can be installed on either a new or existing site, we strongly recommend making a complete backup of your existing site before applying any features included in this plugin.
- Плагин работает на любых серверах либо хостингах?
- iThemes Security requires Apache or LiteSpeed and mod_rewrite or NGINX to work.
- While this plugin should work on all hosts with Apache or LiteSpeed and mod_rewrite or NGINX, it has been known to experience problems in shared hosting environments where it runs out of resources such as available CPU or RAM. For this reason, it is extremely important that you make a backup of your site before installing on any existing site. If you run out of resources during an operation such as renaming your database table, you may need your backup to be able to restore access to your site.
- Finally, please make sure you have adequate RAM if you plan to use the file change detector or make large backups.
- Does this work with network or multisite installations?
- Yes. We’re in the process of developing more documentation, so we’ll update this as soon as it’s ready.
- Могу ли я помочь?
- Of course! We are in constant need of testers. In addition, we can always use help with translations for internationalization. For more information on contributing to iThemes Security, visit this page.
- What changes does this plugin make that can break my site?
- iThemes Security makes significant changes to your database and other site files which can be problematic for existing WordPress sites. Again, we strongly recommended making a complete backup of your site before using this plugin. While problems are rare, most support requests involve the failure to make a proper backup before installation. DISCLAIMER: Under no circumstances do we release this plugin with any warranty, implied or otherwise. We cannot be held responsible for any damage that might arise from the use of this plugin.
- Note that renaming the wp-content directory will not update the path in existing content. Use this feature only on new sites or in a situation where you can easily update all existing links.
- Fixing iThemes Security Lockouts
- What is Changed By iThemes Security
- Я включил опцию «Принудительно SSL», и мой сайт перестал работать. Как я могу вернуться обратно?
- Откройте файл wp-config.php в текстовом редакторе и удалите следующие 2 строки:
- define(‘FORCE_SSL_LOGIN’, true);
- define(‘FORCE_SSL_ADMIN’, true);
- Где я могу получить помощь, если что-то пойдет не так?
- Official support for this plugin is available for iThemes Security Pro customers. Our team of experts is ready to help.
Free support may be available with the help of the community in the WordPress.org support forums (Note: this is community-provided support. iThemes does not monitor the WordPress.org support forums).
Installed on a couple sites and with latest update locked me out of wp-admin. Luckily had backup I could restore to. Support wouldn't even help me to remove their terrible plugin.
newest update - server error 500
- Bug Fix: When a requesting IP address cannot be found, default to 127.0.0.1. This fixes issues with some alternate cron setups.
- Bug Fix: Having more than one iThemes Security modification in a .htaccess, nginx.conf, or wp-config.php file will no longer result in having all the file content between each section removed when updating the file.
- Bug Fix: Modifications to the wp-config.php file added by W3 Total Cache now have their Windows-style newlines preserved when iThemes Security updates the file.
- Enhancement: Improved plugin performance by reducing the number of queries made on each page.
- Enhancement: Reduced memory and CPU usage due to various code improvements.
- Bug Fix: A database backup will no longer be created when first activating the plugin.
- Bug Fix: Added compatibility for MySQL strict mode in database creation syntax.
- Bug Fix: Removed warning about a «non well formed numeric value encountered» in PHP 7.1.
- Bug Fix: Modifications to wp-config.php, .htaccess, and nginx.conf files are now properly re-added upon reactivation.
- Bug Fix: Fixed full settings for Hide Backend being displayed after disabling the feature and saving the settings.
- Bug Fix: Enabling or disabling the Hide Backend feature will update the «Log Out» link so that it works as expected without having to load a new page.
- Bug Fix: Enabling or disabling the Hide Backend feature now properly updates the .htaccess/nginx.conf file on enable and disable rather than at some future point.
- Bug Fix: Fixed issue that could cause improper database table creation on multisite sites.
- Bug Fix: Fixed a bug that could prevent settings from saving properly if the site was migrated to a new server or a new home path on the server.
- Bug Fix: Fixed bug that prevented Away Mode from activating on some sites.
- Enhancement: Added logging for failed two-factor, OAuth, and REST API authentications.
- Enhancement: Added logging details about the source of login failures and the type of authentication that failed.
- Enhancement: Due to improvements in tracking authentication failures, brute force attempts using alternate authentication methods are more reliably found and blocked.
- Enhancement: The server’s IP is treated as whitelisted and will not be considered for lockouts or bans.
- Enhancement: Reduced memory usage when creating a backup.
- Enhancement: Changed log entry description of «IP Flagged as bad by iThemes IPCheck» to «IP Flagged by Network Brute Force Protection». This should help clarify the meaning of the log entry.
- Enhancement: Improved efficiency of the Network Brute Force Protection feature.
- Bug Fix: Fixed bug that prevented Network Brute Force Protection from working properly on some sites.
- Bug Fix: Removed «comodo» from the list of user agents blocked by the HackRepair.com blacklist. This ensures that Comodo’s AutoSSL feature of cPanel/WHM is able to function.
- Updated Feature: Updated the «REST API» feature in the WordPress Tweaks section. The feature now has proper support for protecting privacy on your site without preventing the REST API from functioning.
- Enhancement: Updated Security Check to enforce setting the «REST API» setting to «Restricted Access».
- New Feature: Added a «REST API» feature in the WordPress Tweaks section. This new feature allows you to block or restrict access to the REST API.
- Bug Fix: Fixed issue that could cause database backup emails to be sent without the backup zip attached.
- Enhancement: Updated the lockouts notification email to a new design. This new design also cleaned up the translation strings to allow better translations.
- New Feature: Added a «Protect Against Tabnapping» feature in the WordPress Tweaks section. Details of what this feature protects against can be found here: https://www.jitbit.com/alexblog/256-targetblank—the-most-underestimated-vulnerability-ever/
- Misc: Updated the description for the Lockout Period setting to indicate that the default value of 15 minutes is recommended.
- Bug Fix: Remote IP is now correctly identified if the server is behind a reverse proxy that sends requests with more than one IP listed in a single header.
- Bug Fix: Fixed the link for a user in the logs page so that it properly works on sites that are inside a subdirectory.
- Bug Fix: Improved how Strong Password Enforcement works on password resets to improve compatibility with various plugins.
- Bug Fix: Improved the logic for determining whether a user should have Strong Password Enforcement applied. This covers situations where the user may have a custom role, a customized default role, or added capabilities beyond their role.
- Enhancement: Improved the logic for determing the requesting IP address to better handle situations where the site is behind a reverse proxy.
- Enhancement: Strong Password Enforcement now uses a PHP port of zxcvbn to ensure that a strong password was selected.
- Enhancement: All links in Security that have target=»_blank» now have added rel attributes to protect against tabnapping.
- Misc: Updated remaining ip-lookup.net links to instead link to traceip.net in keeping with other links that were previously updated to traceip.net.
- Bug Fix: Fixed data save issue that could cause multiple notification emails to be sent in a short period of time.
- Bug Fix: Fixed issue that could cause the malware scanner to fail on sites that change the arg_separator.output php.ini value from its default value.
- Bug Fix: Removed redundant entries in the HackRepair blacklist.
- Bug Fix: Enabling Protect System Files in System Tweaks will now only block install.php for the current site. This fixes the issue where the setting can block installation of a site in a subdirectory.
- Bug Fix: Fixed problem that could cause requests for iThemes Security data from iThemes Sync to fail due to large amounts of log entries.
- Bug Fix: Scheduled backups now run if the ITSEC_BACKUP_CRON define is set with a non-boolean value.
- Bug Fix: Replaced static references to wp-includes with the WPINC define.
- Bug Fix: Moved blocking of query strings containing %0[0-9A-F] characters from the Non-English Characters setting to the Suspicious Query Strings setting as those characters are control code characters and are not associated with a language.
- Bug Fix: Added escaping to some translation strings.
- Bug Fix: Removed unused files from the WordPress Tweaks module directory.
- Bug Fix: Fixed the Daily Digest email reversing the user and host lockout counts.
- Bug Fix: The database backup email no longer sends from the email address configured in Settings > General. It now defaults to the same from address that the wp_mail() function uses. This will fix the mail being blocked by some mail servers due to a spoofed from address.
- Enhancement: Updated the server config rules generated by the System Tweaks settings. They are now more consistent between Apache, LiteSpeed, and nginx. They are also more efficient and have been improved to limit accidentally blocking non-targeted requests.
- Enhancement: Updated the database backup email to a new design.
- Enhancement: Added a note that the Filter Request Methods setting in System Tweaks should not be enabled if the WordPress REST API is used. This is becasue the DELETE HTTP method is blocked when the setting is enabled.
- New Feature: Added setting to block requests for PHP files in the plugins directory in System Tweaks.
- New Feature: Added setting to block requests for PHP files in the themes directory in System Tweaks.
- Bug Fix: Fixed issue that reported invalid counts for host and user lockouts in the daily digest email.
- Bug Fix: Fixed issue that caused the daily digest email to be sent every day, even if no lockouts occurred and no file changes were found.
- Bug Fix: Fixed issue that could prevent saving of File Change settings, resulting in an error messages of «A validation function for file-change received data that did not have the required entry for latest_changes.»
- Bug Fix: Fixed iThemes Security Pro logo appearing in daily digest emails.
- Bug Fix: Removed the «Wget» user agent from the Hack Repair blacklist as it can block wp-cron jobs on some hosts.
- Bug Fix: Fixed error «PHP message: PHP Fatal error: ‘continue’ not in the ‘loop’ or ‘switch’ context».
- Enhancement: Added new Daily Digest email design.
- Security Fix: Fixed issue where a locked out but not yet blacklisted IP/user could receive different HTTP headers when testing a valid username/password combination. Thanks Leon Atkinson of 18INT for contacting us about this issue.
- Security Fix: Updated log output to prevent specific kinds of logged requests from displaying without sanitization. Thanks to Slavco Mihajloski for contacting us about this issue.
- Bug Fix: The Security > Security Check link now works as expected in multisite.
- Bug Fix: Fixed bug that could prevent the «Filter Long URL Strings» feature from working properly.
- Bug Fix: Removed restrictions in the «Filter Long URL Strings» feature that were unrelated to request length.
- Bug Fix: Corrected a settings description typo in Global Settings.
- Bug Fix: Fixed bug that could result in issues authenticating over XML-RPC when the WordPress Tweaks > Multiple Authentication Attempts per XML-RPC Request setting is set to «Block».
- Misc: Added placeholder for the Version Management module of iThemes Security Pro.
- Misc: Updated build number to trigger some updates.
- Bug Fix: Fixed a potential logging issue that could prevent some lockout notices from being properly logged on non-English sites.
- Bug Fix: Prevented some notices from displaying to users who do not need to see them.
- Bug Fix: Limited notices to only display on specific pages on the dashboard.
- Compatibility Fix: Changed name of the $HTTP_RAW_POST_DATA variable to avoid erroneously tripping PHP 7 compatibility checks.
- Code Cleanup: Removed legacy code that is no longer needed.
- Enhancement: Started tracking when a user was last seen as logged in and active for future use.
- Misc: Added a placeholder for the Pro feature «User Security Check».
- New Feature: Added a new Security Check section on the settings page. This new feature adds a tool to quickly ensure that the recommended features are enabled and the recommended settings are used.
- Bug Fix: Fixed the ability to remove the itsec_away.confg file in order to disable Away Mode.
- Enhancement: The «Ban Lists» setting of Banned Users is now enabled by default.
- New Feature: Added a new File Permissions section on the settings page to bring back the directory and file permissions listing feature found on the Security > Dashboard page of older plugin versions.
- Bug Fix: Fixed a situation where adding a very large list of IP’s in the Ban Hosts list would generate an invalid .htaccess file on some servers.
- Enhancement: The Database Backups, Local Brute Force Protection, Network Brute Force Protection, Strong Password Enforcement, and WordPress Tweaks features are now active by default on new installations.
- Enhancement: The WordPress Tweaks feature now uses the «Disable File Editor» setting by default on new installations.
- Enhancement: The WordPress Tweaks feature now sets the «Multiple Authentication Attempts per XML-RPC Request» setting to «Block» by default on new installations.
- Enhancement: Improved the styling of notices.
- Bug Fix: Fixed SQL query for Database Backups when «Backup Full Database» is enabled.
- Bug Fix: Fixed bug that could cause some sites to lose settings when upgrading.
- Bug Fix: Fixed links to Settings, Logs, and creating a backup on Multisite.
- Enhancement: The «Write to Files» setting is now enabled by default.
- Bug Fix: Fixed error that would prevent nginx servers from being able to make use of the «Reduce Comment Spam» feature of the WordPress Tweaks module.
- Bug Fix: Restored missing log filter for 404 Detection log entries.
- Enhancement: New user interface with both grid and list views for managing settings.
- Enhancement: New automatic temp whitelisting of IPs for users that manage iThemes Security settings.
- Enhancement: Better feedback on errors when modifying wp-config.php or server config files.
- Enhancement: Improved code efficiency of the Away Mode feature so that it takes less processing time when active.
- Enhancement: Rather than disabling features that have invalid user input, the user now can fix the issue before saving.
- Enhancement: Improved the efficiency of the plugin’s loading code, reducing the amount of time taken to run the plugin.
- New Feature: Global settings now has a «Show Error Codes» setting that can provide an error message’s specific error code when it is enabled.
- Bug Fix: More than one IP can now be temp whitelisted.
- Bug Fix: Fixed a bug where some modules would be enabled or disabled when they shouldn’t be after upgrading to the latest version.
- Bug Fix: Will not send notification emails about the new login address when Hide Backend is enabled and doing an upgrade.
- Compatibility Fix: Updated handling of wp_remote_get() responses in preparation for changes coming in WordPress 4.6.
- Bug Fix: Throw a real 403 instead of a faked 404 for hide backend — Fixes compatability with certain plugins including WordPress SEO. Hat tip to Joost de Valk (@jdevalk) and the @Yoast team for bringing this issue to our attention.
- Security Fix: Better caps checks for dismissal of changed file dialog — Thanks to Julio Potier for notifying us of this issue.
- Bug Fix: Make file change warning dialog text properly translatable
- Enhancement: Adding ‘itsec_log_event’ action for logged events
- Security Fix: No longer using document.location to build ‘Show Intro’ link in admin — Thanks to David Lodge (Pen Test Partners) for notifying us of this issue.
- Bug Fix: Fixed some notices when certain multisite options are used on BuddyPress
- Enhancement: New itsec_white_ips filter to allow plugins that work with external services to whitelist service IPs
- Bug Fix: Fixed issue that could cause a fatal error after changing the content directory.
- Bug Fix: Updated the link to sign up for security guide download to point to a https address. This is better security and prevents warnings when submitting from a http site in some browsers.
- Bug Fix: If a cryptographically secure log file name can’t be generated, queue up log file writes until we can.
- Bug Fix: Fixed temporary whitelisting by preventing a temporarily whitelisted IP from being locked out.
- Bug Fix: Updated code that generates the backups and logs directories to ensure that it attempts to create the parent directory if it does not exist yet.
- Bug Fix: Removed warnings that could be generated if the logs directory could not be created.
- Bug Fix: Database backup files sent via email no longer have a name without an extension if zipping up the file fails.
- Security Fix: Hardened the created backups and logs directories. Thanks to Nicolas Chatelain (SYSDREAM IT Security Services) for notifying us of this issue.
- Security Fix: More secure backup and log file names. Thanks to Nicolas Chatelain (SYSDREAM IT Security Services) for notifying us of this issue.
- Bug Fix: The «NGINX Conf File» setting is now properly respected, causing the generated NGINX configuration file to be stored in that location.
- Enhancement: Generated database backup file names now contain a human-readable timestamp in the format of YYYYMMDD-HHMMSS.
- Enhancement: Zipped database backup files no longer contain a deeply nested directory structure. Instead, they only contain the sql file.
- Enhancement: When the «Force Unique Nickname» feature is enabled, the generated display name now uses an improved randomization function.
- Enhancement: Improved tabbing of rules in generated nginx.conf files.
- Enhancement: Removed the «See what’s new button» as it has fulfilled its purpose.
- New Feature: Added support for IPv6 addresses. This includes support for IPv6 in lockouts, ban hosts, and white lists.
- Bug Fix: Fixed issue that could cause username-based lockouts to fail for long usernames.
- Bug Fix: Fixed issue that prevented wildcard IP ranges from being blacklisted or whitelisted.
- Bug Fix: Removed warnings generated when the Away Mode module is disabled and iThemes Sync contacts the site.
- Enhancement: Updated descriptions of valid IP and IP range formats for the Lockout White List and the Ban Hosts settings.
- Enhancement: Updated host entries in log details to link to traceip.net rather than ip-adress.com. This is because ip-adress.com does not support IPv6 addresses.
- Enhancement: Updated some translatable strings relating to blacklisting and whitelisting to allow for better translations.
- Enhancement: Added details about how wildcard IP ranges are converted to CIDR format (this improves performance).
- Bug Fix: Comparisons of IPv4 addresses and ranges now include the IP’s at the edge of the ranges.
- Bug Fix: IPv4 tests now work as expected when deciding if a blacklisted IP or range overlaps a whitelisted IP’s and ranges.
- Bug Fix: Fixed styling issue that affected the display of the horizontal tabs on settings pages in WordPress 4.5.
- Bug Fix: Replaced old module sorting order in settings screens.
- Bug Fix: Fixed PHP 7 compatibility issue that triggers the following error: «Uncaught Error: Call to undefined function mysql_get_client_info()».
- Bug Fix: Fixed warnings and errors that could occur when deleting the plugin.
- Bug Fix: Fixed warning that could occur on a failed login when Local Brute Force Detection is disabled.
- Bug Fix: All data added to the options table by iThemes Security is removed on uninstall.
- Bug Fix: Fixed the cause of the following warning: call_user_func_array() expects parameter 1 to be a valid callback, class ‘ITSEC_SSL_Setup’ does not have a method ‘execute_deactivate’
- Enhancement: When a lockout is being executed, wp_logout() will only be called if the current page request comes from a logged in user. This prevents plugins that log logout events from logging log outs from unknown users.
- Enhancement: Improved the descriptions used for some of the data displayed in the «System Information» section of Security > Dashboard.
- Enhancement: Added «Use MySQLi» entry to the «System Information» section of Security > Dashboard to show whether the MySQLi driver is enabled.
- Enhancement: Updated the «SQL Mode» entry in the «System Information» section of Security > Dashboard to show the full details if that value is set.
- Enhancement: Improved code that ensures that tables and options table entries created by iThemes Security are removed on uninstall only when no other iThemes Security plugin is active.
- Security Fix: Fixed PHP code that could allow AJAX requests to list directories and files outside the directory structure of the WordPress installation. Note that these AJAX requests required a logged in user with admin-level privileges. This vulnerability was unable to be exploited by non-privileged or anonymous requests.
- Bug Fix: Updated the SSL feature to use 301 redirects rather than 302 redirects.
- Bug Fix: Fixed situations where security nonces would incorrectly trigger «security check» errors when enabling specific combinations of features on the settings page.
- Bug Fix: Enabling scheduled database backups and setting a backup interval of 0 days no longer results in a backup being created on every page load.
- Bug Fix: Module-specific data is properly initialized/removed on plugin activation, deactivation, and uninstallation.
- Feature Removal: Removed the «Security Status» portion of the Security > Dashboard page. This is in preparation for a new tool that provides suggestions tailored to the site and server that Security is running on.
- Enhancement: Updated the way the feature modules function in order to allow them to be redesigned in a more efficient and flexible way for future releases.
- Enhancement: Updated the File Change Detection feature to attempt a max memory limit of 256M rather than 128M as some users experience out of memory issues which could be fixed with the higher memory limit.
- Enhancement: Updated the Database Backup feature to attempt a max memory limit of 256M rather than 128M as some users experience out of memory issues which could be fixed with the higher memory limit.
- Enhancement: Added localization support for some non-localized strings.
- Enhancement: Improved detection of multiple active versions of iThemes Security.
- Enhancement: Removed Yandex and Sogou from the HackRepair blacklist as they are legitimate search engine bots.
- Enhancement: Added detailed information about Sucuri malware scan errors to Malware Scan log details.
- Bug Fix: No longer enables display of database errors when an event is logged.
- New Feature: Added «Multiple Authentication Attempts per XML-RPC Request» setting to the WordPress Tweaks section. When this setting is set to «Block», iThemes Security will block brute force login attacks against XML-RPC as described by Sucuri in this blog post: https://blog.sucuri.net/2015/10/brute-force-amplification-attacks-against-wordpress-xmlrpc.html
- Enhancement: Updated text describing the XML-RPC setting in the WordPress Tweaks section to better explain what the setting is for and which setting is recommended.
- Enhancement: Improved IP detection when proxy detection is active by processing the header set by CloudFlare.
- Enhancement: Added a filter named itsec_filter_remote_addr_headers which can be used to change which headers are searched for the client IP. This allows for tailoring the IP detection for specific reverse proxies and load balancers.
- Bug Fix: Updated the Banned Users settings to no longer add a newline to the Ban Hosts input each time the settings page is saved.
- Compatibility Fix: Updated code triggered by the ITSEC_TEST_MALWARE_SCAN_DISABLE_SSLVERIFY define. This avoids plugin compatibility issues that prevent disabling the SSL peer verification.
- Compatibility Fix: Added support for ITSEC_TEST_MALWARE_SCAN_DISABLE_SSLVERIFY. Setting it to true can bypass «SSL peer certificate or SSH remote key was not OK» errors on servers with bad SSL configurations.
- Compatibility Fix: Changed translation domain from it-l10n-better-wp-security to better-wp-security. This change was necessary in order to be included in the translate.wordpress.org project.
- New Feature: Added malware scanning provided by Sucuri SiteCheck.
- Feature Removal: Removed the «Remove WordPress Generator Meta Tag» and «Display Random Version» features as they are not recommended due to limited security benefit and creating compatibility issues.
- Enhancement: Added the ability to undo the Content Directory change.
- Bug Fix: Fixed an issue with one-time database backups on multi-site installs.
- Bug Fix: Fixed issues related to locating .htaccess or nginx.conf files on sites with WordPress installed in a separate directory.
- Bug Fix: Fixed issues with PHP blocking in uploads directory not working with certain non-standard setups.
- Bug Fix: Minor change to fix a warning that can appear after changing the Content Directory.
- Bug Fix: Fixed a PHP fatal error that could occur on some servers when adding a ban to the site’s .htaccess or nginx.conf file.
- Feature Removal: Removed the malware scanning features as VirusTotal no longer supports scanning from WordPress sites. A replacement is in the works.
- Bug Fix: The close button on the «Thank you for activating iThemes Security» message now appears in the correct location.
- Bug Fix: Removed the site’s URL being displayed in the «Replace jQuery With a Safe Version» setting details.
- Bug Fix: Updated .htaccess rules to be compatible with Apache 2.4 without the auth compat module.
- Bug Fix: Enabling and disabling the «Remove File Writing Permissions» setting now updates the file permissions properly.
- Bug Fix: Web servers that cannot be recognized now default to Apache.
- Enhancement: Updated the hackrepair lists.
- Enhancement: Updated to use new file modification API.
- Enhancement: Added HackRepair.com blacklist for Nginx.
- Enhancement: Improved Nginx support for System Tweak features.
- Enhancement: Updates to wp-config.php, .htaccess, and nginx.conf files now support more systems.
- Enhancement: Combined the «Force SSL for Dashboard» and «Force SSL for Login» settings to a unified «Force SSL for Dashboard» setting. This is due to how the FORCE_SSL_LOGIN define was deprecated in WP 4.0.0.
- Enhancement: Added comments to wp-config.php, .htaccess, and nginx.conf updates that indicate which settings affect the specific entries.
- Enhancement: Added translation support for previously static strings, including strings used for comments in wp-config.php, .htaccess, and nginx.conf files.
- Enhancement: Improved generation of valid referers for use by the Reduce Comment Spam feature.
- Enhancement: Broadened the server support in the import settings code.
- Enhancement: Added new library classes for managing files, directories, and config files.
- Enhancement: Improved error messages for when file writes fail.
- Enhancement: Improved error messages for when export file creation fails.
- Enhancement: Improved error messages for situations when the .htaccess, nginx.conf, or wp-config.php files may need to be manually updated.
- Bug Fix: Added support for Apache 2.4 without the access_compat module.
- Bug Fix: Fixed condition where forcing SSL on front-end pages could cause infinite redirection loops with specific setups of nginx to Apache reverse proxy servers.
- Bug Fix: Fixed scenarios where the site would be forced to load via https but scripts, stylesheets, and images would load via http.
- Bug Fix: Fixed invalid nginx.conf rule generation for the Reduce Comment Spam feature.
- Bug Fix: Corrected invalid parsing of some IP formats in Ban Hosts list.
- Bug Fix: Improved error handling when reading or updating config files.
- Bug Fix: Fixed various warnings that would display when changing settings.
- Bug Fix: Fixed a situation where creation of a zipped export file would fail, but an email would still be sent as if the zip was created successfully.
- Security fix for XSS vulnerability. Thanks to Ole Aass (@oleaass) for finding and disclosing this vulnerability to the iThemes Security team.
- Enhancement: Translation files can now be stored in WP_LANG_DIR/plugins/better-wp-security/ so that translation files will not be overwritten on when the plugin updates.
- Bug Fix: The file permissions check will no longer list a warning if the plugins directory has permissions of 755.
- Bug Fix: Fixed incorrect text describing the «Backups to Retain» database backup setting.
- Bug Fix: Fixed regression that prevented adding wildcard IP’s in the form of ‘XXX.XXX.XXX.*’ to Ban Hosts.
- Bug Fix: When a file scan is run from iThemes Sync, a warning will no longer be added to the site’s error log.
- Enhancement: Minor refactoring for performance and scalability.
- Enhancement: Add ITSEC_BACKUP_CRON constant to replace plugin’s backup scheduler with wp_cron.
- Enhancement: Add dashboard reminder to salts to prompt for periodic salt changes.
- Enhancement: Limit the number of lockouts that can be displayed at any given time in the dashboard.
- Fix: Make sure header error messages are suppressed when performing a lockout.
- Fix: Fix error message from missing login information when displaying lockouts.
- Fix: Quick banning IPs will now work correctly if existing htaccess rules are in place
- Fix: minor bug fixes and typo corrections.
- New Feature: Change WordPress Salts
- Enhancement: Refactored ITSEC_Lib and ITSEC_Files for better usability and new functions to make changing salts possible
- Fix: Fixed typo on file change warning emails.
- Fix: Fixed duplicate module listsing on log page dropdown
- Fix: Fixed missing lockouts on iThemes Sync dashboard
- New Feature: Add file/folder permissions check to Dashboard
- Fix/Enhancement: Code refactoring of numerous modules
- Fix: Hiding available updates in multi-site will no longer block wp-cli from detecting updates.
- New Pro Feature: Google reCAPTCHA
- Fixed: Removed unneeded fields in malware
- New Pro Feature: wp-cli integration
- New Feature: Temporarily whitelist your IP address via iThemes Sync
- New Feature: Override proxy IP detection
- New feature: Hide admin bar (if desired)
- New Feature: Perform file scan via iThemes Sync
- New Feature: Perform malware scan via iThemes Sync
- Enhancement: Added filter to allow for custom log pages
- Enhancement: Added debug constant to help troubleshoot multiple emails
- Enhancement: Added constant to force digest emails via wp-cron instead of custom timing
- Fixed: Various missing variable fixes were added
- Fixed: MySQL errors on MySQL 5.6 during activation were fixed.
- Fixed: HTML emails now contain HTML tag
- Fixed: Lockout count in emails should now be more accurate
- Fixed: Make sure to esc urls on SSL redirects (unreported minor security fix)
- Fixed: Added filters to SSL to try to catch more assets
- Fixed: Suspicious query strings feature should no longer conflict with many plugins
- Fixed: File change detection should no longer throw an error if opendir failed
- Fixed: App passwords in two-factor authentication will now correctly authenticate themselves.
- New Pro Feature: Temporary privilege escalation
- Enhancement: More time/date information is now shown in the logs for file change scanning
- Fixed: Filechange will no longer show false positives with every change in DST (although this will cause run round of such notifications on update).
- Fixed: Link to malware scanning logs will work.
- New Pro Feature: File change scanning will now compare WordPress core files to the WordPress.org repository.
- Fixed: Make sure php_gid is always defined to prevent error message if the function is not usable.
- Fixed: Link to BackupBuddy in admin bar will now work correctly.
- New Pro Feature: Dashboard widget. Get important information and handle user blocking right from the WordPress Dashboard.
- Fixed: When using wp-cron for file checking cron check will run daily instead of hourly.
- Fixed: Error on line 1312 when iThemes API is actived with version 4.4.15
- Enhancement: File change summary emails are more concise and will avoid extra information
- Fixed: Hide backend will now work with Jetpack’s JSON API authorization.
- Fixed: Option to change user ID 1 will correctly disappear when not present
- Fixed: Removed empty user agent from default blacklist to avoid issues with external services
- Fixed: File change folder check will no longer scan directories outside of ABSPATH for any reason
- Fixed: Adding define( ‘ITSEC_FILE_CHANGE_CRON’, true ); to wp-config.php will cause the file change scanner to only run once daily via wp-cron.
- Fixed: Compatibility issue where strong password enforcement could cause an error if passwords are changed outside of the core of WordPress
- Fixed: Lost password url should now be correct on multisite.
- Fixed: fixed duplicate ID issue from user_id_exists calls.
- Fixed: Fixed an error in the lockout module that results in an error for users of multisite
- Fixed: Notification emails will no longer send if not turned on
- Fixed: Duplicate messages will not be allowed in digest emails
- Fixed: Duplicate digest emails will have a far lesser chance of sending
- Fixed: User lockout count in email notifications will now be correct
- Enhancement: Default log rotation changed from 30 days to 14 days
- Fixed: All logs page will properly display even with 50,000+ entries in the log
- Enhancement: Updated copy on Virustotal API key to indicate that a private key is not needed.
- Fixed: More complete check for user id when resettings password will prevent undefined index login on line 62 error.
- Fixed: Fixed a bug that prevented the api key from saving after resetting the key.
- Fixed: Removed errors that could occur due to the use of custom capabilities and roles.
- New Pro Feature: Automatically generate strong passwords
- New Pro Feature: Password expiration
- Enhancement: Added a link to the actual timezone settings in the general settings page (instead of the top of the page)
- Fixed: When an invalid log directory is detected it will not fail but will instead reset it to the original.
- Fixed: No more duplicate digest emails
- Fixed: No more «Array» message appearing in digest emails from user lockouts
- Fixed: HTML in traditional file log emails will display correctly.
- Fixed: From address in notification emails will now display correctly.
- Fixed: MySQL errors will no longer appear for missing iThemes Security tables. Instead it will attempt to recreate them.
- Fixed: Fixed missing «no changes» text in file change emails.
- Fixed: Formatting of individual file change emails will now work.
- Fixed: Fixed a bug in ban users user agents that would cause a crash on Apache if the user agent contained a space
- Fixed: When an invalid backup directory is detected it will not fail but will instead reset it to the original.
- Fixed: fixed possible undefined api_error variable on line 316 if WordPress believes the email address is invalid.
- Fixed: failed calls to various apis will no longer throw a php error on failure.
- Fixed: Fixed typos in digest email.
- Fixed: Fixed typos in default network lockout message.
- Fixed: Force stylesheet reload for new nags and other items by pushing plugin build number to stylesheet registrations
- Fixed: Fixed an error that could occur on multisite due to a missing «core» object
- New Feature: Add IPCheck Brute Force API integration
- New Feature: Add ability to receive a daily digest email instead of individual emails per event.
- Enhancement: Added «Go Pro» menu item to admin menus.
- Enhancement: Added button to release IP address from temporary whitelist.
- Enhancement: Reordered sidebar items to make it easier for the user to get to the information they need from iThemes
- Fixed: introduction screen should now display completely on computers with low-resolution screens.
- Fixed: multisite bug that still showed BackupBuddy (if present) even though BackupBuddy is not multisite compatible.
- Fixed: Scrolling table of contents should not cover side-bar items on pro.
- Fixed: When changing admin user login form will no show the correct path when WordPress is not installed in the same directory as the website address.
- Fixed: The plugins_loaded hook which fires on logout will now fire later to improve compatibility with iThemes Exchange
- Fixed: multisite bug that still showed BackupBuddy (if present) even though BackupBuddy is not multisite compatible.
- Fixed: Added an extra flag in an attempt to reduce duplicate file-change detection executions.
- Fixed: Added missing index.php files to directories that were missing them to ensure no information could be attained if directory is turned on.
- Fixed: Make sure hide backend rewrite rules are consistent with the correct location of the WordPress login page when WordPress is not installed in the main website folder.
- Fixed: File locking will try to create the iThemes Directory if it isn’t already present rather than just saying a lock could not be attained.
- Fixed: Fixed an error whereas an empty filter could display an error when building the log tables.
- Low Severity Security Fix — Lack of access control patched — Sucuri (reported 19Aug2014)
- Fixed an error in XMLRPC blocking when $username variable cannot be found
- Remove error message if WP_Error is returned with wp_remote_post in malware scan
- Fixed bug where away-mode was still enabled after one-time period has passed which could result in away mode activating when it should not
- Ensure that individual module updates fire when updating the plugin
- Added function to retrieve current URL from the front-end
- Fixed error in brute force protection that counts valid logins with XML-RPC as bad logins towards a brute force lockout
- Updated descriptions an instructions in malware scheduling to make the feature easier to use
- Numerous typo corrections throughout dashboard
- Clean up notifications for file change detection and malware scanning
- Fixed an accidental disabling of file change scans introduced in 4.3
- Added on-demand malware scanning for the homepage
- Added better URL validation to ITSEC_LIB
- Added exception for 127.0.0.1 to prevent a local server from being locked out of a site during wp-cron or other calls
- Added button to quickly add current IP address to permanent whitelist
- Added appropriate message for logs page when logs are not available due to «file only» logging being selected
- Fixed Error in 404 scanning if path field was empty
- Updated hackrepair.com’s default blacklist
- Modified support reminder to ask users to upgrade rather than donate
- Use get_home_path() in place of ABSPATH to account for WordPress core in a different directory than wp-content
- Use PHP comments in index.php file to account for the possibility of a scan including the file in which case the html comment could result in an error
- Fixed various typos throughout the plugin dashboard
- Added ability to prevent file change scanning from running on a given page load by defining ITSEC_FILE_CHECK_CRON to true
- Cleaned up file change logging reports to me more clear when no files have been changed
- Added feature to immediately ban user «admin» when no user «admin» exists on the site and a host tries to log in with it anyway
- Added blank line to end of all textarea input to make it easier to input data
- Added brute force checks to XMLRPC calls to prevent brute force attacks against XMLRPC
- Fixed a bug preventing file-change scanning from running when manually executed from the «Logs» page
- Fixed a bug where an error could be generated if the saved files from the file change feature weren’t properly saved
- Fixed comment approval email links to make sure they work when a user is not logged in and hide backend is in effect
- Fixed an issue that was preventing an IP from being permanently banned due to too many lockouts
- Updated .htaccess rules for an IP that has been banned from too many lockouts to be more effective in more hosting environments
- Fixed responsive issues in iThemes notifications that prevented notifications from being easily read on small screens.
- Fixed error for missing function in hide backend
- Fixed an error that could cause a 404 on the admin with hide-backend enabled.
- Fixed error on line 55 of class-itsec-four-oh-four.php that could occur under certain circumstances
- Don’t filter hide backend hash until after schema redirect
- don’t send file change email on first scan
- Fixed verbage when changing login URL
- Modified ban users rewrites for apache. Should work with proxy and if setenvif isn’t enabled.
- Fixed get_module_path to prevent 404 errors on plugin assets
- Fixed misplaced parenthesis forcing computer to always display it isn’t whitelisted
- Updated readme.txt
- Added call to settings import/export module (pro)
- Added button to restore default log location
- Don’t automatically load front-end classes in dashboard pages
- Avoid errors on save if htaccess is completely empty
- Only register activation/deactivation/install hooks in admin
- Make sure temporary white-list is always available
- Improved check for white-listed IP during lockout
- Added ability to use constant to override server detection
- Don’t remove extra line spaces in .htaccess
- Minor reformating and typo fixes
- Make sure front-end classes are available only when needed
- Fixed default types in file change settings
- Added file type exclusion to 404 settings
- Allow for Jetpack SSO to function with suspicious queries turned on
- Use WordPress’ PclZip for backup zip
- Make sure backup disables itself when other backup solutions are present
- Fix tweet link
- Minor fixes and cleanup
- Added call to two-factor module
- Consolidate white lists into one option
- Fix IP mask calculations
- Fix NGINX IP range blocking
- Update modules to use new logging
- Minor refactoring
- Add metabox for iThemes Sync
- Update jQuery version in tweaks
- Shortened file change array names to save space
- Fixed links in lockout emails
- Fixed IP mask calculations
- Add call to pro user-logging module
- Add ability to temporarily whitelist an IP address
- Don’t allow empty file types in file change exclusions
- Add Sync integration for Away Mode
- Minor typo and other fixes
- Better cache clearing and formatting updates
- Make sure rewrite rules are updated on this update
- Remove extra (settings) items from admin bar menu (leave logs and important information)
- Add WP_CONTENT_DIR to system information on dashboard
- Move support nag to free version only and make sure it properly redirects
- Fix check for presence of BackupBuddy to work with BackupBuddy >=22.214.171.124
- Clean up details views on log pages
- Add username column to temp and lockouts tables
- Lockout usernames whether they exist or not
- Don’t duplicate lockouts
- Fixed malformed lockout error on lockout message
- Don’t display a host lockout when none exists
- Add Sync integration to release lockouts
- Improved reliability of brute force user lockouts
- Miscelaneous typos and other fixes
- Remove extra file lock on saving .htaccess, nginx.conf and wp-config.php. Only flock will be used in these operations
- Fixed a function not found error in the brute force module
- Improved content filtering in SSL so that more images and other content will link with appropriate protocol.
- Fixed hide backend in cases where a lockout has expired
- Miscelaneous typos and other fixes.
- Make sure «remove write permissions» works
- Better descriptions on white list
- Add pro table of contents if needed
- Make sure security admin bar item works
- Make sure lockout message only happens when needed
- Suppress errors on readlink calls
- Make sure class is present for permanent ban
- Make sure white list is an array
- Fix white listed IPs not working
- Log when Away-mode is triggered
- Make sure away mode file isn’t accidently deleted
- Make sure away mode doesn’t even allow access to the login form (as it didn’t in 3.x)
- Enhance warnings on «Change content directory» settings
- Better descriptions on white lists
- Fixed XMLRPC label
- Better XMLRPC Dashboard status
- Don’t allow logout action on wp-login.php with hide backend
- Better check for variable in SSL admin
- XMLRPC soft block should now work with WordPress mobile app
- Make sure uploads directory is only working in blog 1 in multisite
- Better checks for run method in module loader
- Make sure backup directory is present before trying to use it
- Make sure backup file method is respected on all backup operations
- Added ability to limit number of backups saved to disk
- Minor typo and other fixes
- Only load front-end classes as needed
- Add link to free support at .org forums
- Remove select(?ed) from suspicious query strings for 3.9 compatibility
- Fixed domain mapping issue (requires https://wordpress.org/plugins/wordpress-mu-domain-mapping/ domain mapping plugin)
- Remove array type errors on 404 pages
- Remove remaining create function calls
- Make sure logs directory is present before trying to use it
- Log a message when witelisted host triggers a lockout
- Don’t create log files if they’re not going to be used
- Add pro tab if pro modules need it
- Upgrade module loader to only load what is needed
- Fix sorting by count in 404 Logs
- Minor code cleanup
- Make sure all wp_enqueue_script dependencies are in proper format
- Reduce priority of hide backend init for better compatibility with other plugins
- SSL now logs users out when activating to prevent cookie conflicts
- When activating SSL Log out the user to prevent cookie conflicts
- Use LOCK_EX as a second file locking method on wp-config.php and .htaccess
- Minor code cleanup
- Make sure all wp_enqueue_script dependencies are in proper format
- Added ability to «soft» block XMLRPC to prevent pingback vulnerability while still allowing other access
- Updated «Suspicious queary strings» to not block plugin updates
- Update NGINX comment spam rewrite rules to better work with multi-site domain mapping
- Move 404 hook in hide backend from wp to wp_loaded
- Make sure super-admin role is maintained on multi-site when changing user id 1 and admin username at the same time
- Make sure all redirects for hide backend and ssl are 302, not 301
- Better resetting of SSL and disallow file editor on deactivation to account for more states
- Make sure hide backend works with registration
- Minor copy and other fixes
- Update nginx rewrite rule on comment spam when domain mapping is active
- Added the ability to disable file locking (old behavior)
- Better file lock release (try more than 1 method) before failing
- Don’t automatically show file lock error on first attempt
- Added Spanish translation by Andrew Kurtis
- Clean up away mode to prevent lockouts on update or other points
- Make sure unset admin user field remains if the other setting has been fixed
- Removed admin user from settings table of contents
- Make sure array input is trimmed in file change module
- Correct input type on file change settings sanitization
- Use full URL on file change warning redirect to prevent invalid target
- Reduce erroneous hide backend change warnings
- When accessing htaccess or wpconfig make sure opening settings changes are 664 instead of 644 to reduce issues
- Update hackrepair.com’s Agents blacklist
- Make sure global settings save button matches others
- Fixed link in locout email
- Email address settings retain end of line
- Sanitize email addresses on save and not just use
- Make sure whitelist is actually an array before trying to process
- Make sure rewrite rules show on dashboard when file writing isnt allowed
- Added extra information to dashboard server information to help troubleshooting
- Fixed bug preventing file change scanning from advancing when chunked
- Don’t autoload file list on non-multisite installations
- Make sure away mode settings transfer from 3.x or disable away mode
- Better descriptions on save buttons
- Admin use «Fix it» Correctly goes to advanced page
- Execute permanent ban on the correct lockout count, not the next one
- Updated quick ban rules to match standard ban rules (will work with proxy)
- Fixed an NGINX rule that didn’t actually block XMLRPC.php
- Updated rule order on ban users
- Fixed a bug that could prevent away from from turning off in certain time configurations (this resulted in the return to homepage on login)
- Updated some function doc
- Added «Show intro» button next to screen options to bring the intro modal back
- Added ability to use HTML in error messages
- Minor copy and other tweaks
- Private posts will now work with hide backend
- Added an option for custom login action that can bypass hide login
- Allow admin-ajax.php to bypass hide backend
- Added filters for external backup plugins to register with the dashboard
- Enable theme compatibility mode by default
- Miscellaneous copy and function doc fixes
- only save post meta for ssl when the value is true
- fixed missing admin user settings if only one part had been changed
- SSL Redirection working properly on front end. No more redirect errors
- hide backend will warn of the new url when saving
- hide backend will now email the notification email(s) when the login area has been moved
- Added BackupBuddy coupon
- Added ability to manually purge log table
- Removed error message that could happen on user creation with strong passwords enabled
- Moved strong password js later in execution cycle to prevent errors
- More hide backend tweaks to cover remaining white screen issues
- Removed option to enqueue a new version of jQuery unless it is needed
- Removed extra quotes that could appear in user agents
- Removed error message on login page when jQuery replace in use
- Don’t use WordPress rewrites for hide backend, we now create our own rewrite rule
- All modules now use newer upgrade method
- Fix modal dismiss button on settings page
- Ban users rules now should work with proxies
- Saving settings will always generate and write rewrite rules if file writing is allowed
- Hide backend now works with multisite and subdirectory installs
- Make sure tables exist if manually updating from 3.x
- Move admin user settings to advanced page
- Make sure logout happens after processing admin user changes
- All modules now rewritten to call rules on build
- Rename backup and logs folders when wp-content is renamed
- Delay file scan by at least 2 minutes when saving settings
- Added «theme compatibility» mode to remove errors in hide backend caused by themes conflicting with the feature.
- Fixed history.txt (for iThemes customers)
- Moved upgrade to separate function for more seamless update
- Upgrade system rewritten for better functionality
- Make sure 404 doesn’t fail if there is not a 404.php in the theme
- Make sure WordPress root URLs render correctly
- Filewrite now only builds rules on demand.
- Fixed dismiss button on intro modal for small screens
- General cleanup and typo fixing
- New .pot file with updated iThemes .pot file generator
- Fixed away mode not allowing PM times.
- Fixed general copy typos.
- Non super admins will no longer see the «Security» menu item in the admin bar on multisite.
- Update to iThemes’ icon-fonts library to account for ABSPATH set to » or ‘/’.
- Fixed relative paths on Windows servers.
- Removed the pingback URL from the header if XML-RPC disabled.
- Added file locking to admin user operations to [hopefully] avoid duplicated users.
- 404 white list should transfer to global white list
- White list implementation working across all lockouts
- Add extra dismiss box to close welcome modal (fix for smaller screens)
- Fixed bug in conversion of wildcard ip (ie 131.2.1.*) to proper netmask. Should prevent 500 errors on sites.
- Fix for issue whereas a blank deny ip line could be entered into wp-config.php during update if banned users was used.
Better WP Security is now iThemes Security.
This release is a complete rewrite from the ground up. Special thanks to Cory Miller of iThemes.com and Chris Wiegman for realizing the vision for this plugin and how far we can go with it together.
New Security Features
- jQuery Scanner looks for vulnerable versions of jQuery in your theme and gives you the option to replace it with the current version of jQuery from WordPress core.
- Remove author archives for users without any posts. This helps prevent bots from finding users on your site.
- Force a unique nicename. This forces the user to choose a Nickname that is different from the login name which will be used for the author slug and other appropriate areas.
- Disable PHP execution in uploads.
- New UI with streamlined options and other settings
- Hide features not in use
- Smart feature selection for easier use
- Central logs location
- Ability to better customize notification and backup emails by sending to one or more addresses
- Ability to save files anywhere on the host
- Uses file-system locking for all critical operations
- Global settings require setting options only once
- Full BackupBuddy integration
- Voluntary tracking of when options are turned on or off via Google Analytics
- Hide backend no longer uses keys
- Whitelist IPs for all lockouts
- File change detection can run in batches for better resource usage
- Backups can ignore unneeded table data such as logs
- File change detection can ignore specified file types completely
- All saved files now go to uploads
- Ban users now has its own whitelist
- Away mode and nearly all other features tweaked for speed and reliability
- Module feature includes to accommodate future features as well as possibility of 3rd party features
- No more insufficient permissions errors on settings tabs
- Added notice about upgrade
- Reintroduced InfiniteWP compatibility
- Updated readme
- Removed FooPlugins support box as iThemes begins integration of all support
- Removed InfiniteWP Compatibility
- Turned off iThemes Survey
- Updated iThemes email subscription box
- Fixed error message in above support widget when WordPress debug active.
- Fixed error when creating user in iThemes Exchange
- Fixed iThemes image path for case-sensitive
- Add iThemes ITSEC survey to help plan further updates
- Added Customizable email to support form
- Added WP Security Lock as a partner for sites that have already been compromised.
- Changed social information to iThemes
- Better domain support (Mark Boudreau)
- Add username to notification email (Andreas Geibert)
- Changed author to iThemes
- Added links to backup buddy and iThemes subscription
- Fixed inconsistent count in logs
- updated German translation by Rene Wolf
- Updated Bulgarian translation by Martin Halachev
- Removed all instances of the deprecated $wpdb->escape
- Fixed possible XSS issue (Github Issue #64 with patch from i0wn)
- Wrapped all wp_mail calls in function_exists checks as it no longer seems to be reliably available after plugins_loaded in WordPress 3.6
- Minor refactoring
- Added (.*) to Zues in hackrepair.com list to mitigate possible issues
- Typo correction on SSL options courtesy of Roy Randolph.
- Changed minimum version to 3.6
- Fixed error that prevented manual backups from executing
- Updated Turkish translation by Hakan Er
- Updated shield logo by Martin Halachev
- Minor fixes for strict warnings occuring when on PHP 5.4
- Fix for lstat error for files in the ithemes-security/backups/ directory
- Fixed an error that prevented manual filecheck
- Bulgarian translation by Nikolay Kolev of Gymnastics and Bodyweight Tutorials
- Chinese (Traditional) translation by Toine Cheung
- Fixed an XSS vulnerability in the logevent function. Fix by Richard Warren
- Updated Turkish by Hakan Er
- 404 Logs now only accessible via the link on the logs page (thank you Marc-Alexandre Montpas)
- Added .htaccess to protect saved backups (thank you Marc-Alexandre Montpas)
- Added extra sanitization when downloading host info from database (was sanitized on upload) (thank you Marc-Alexandre Montpas)
- Brazilian Portuguese translation by Rafael Funchal
- German translation by Rene Wolf
- Removed timezone from email lockout notifications (GitHub Issue #35)
- Better variable checking to prevent error messages
- Force user 0 when logging filechecking (GitHub Issue #7)
- CSS update for MP6 from shivapoudel
- Small tweak to prevent email notifications being sent when they shouldn’t
- Cleaned up variable checking throughout to eliminate activation errors if php errors or WP_DEBUG is turned on
- Added further checks to reduce errors if file change log is invalid
- Memory should now display correctly in file change email
- Use maybe_unserialize instead of unserialize
- Added option to filter foreign charcters as part of filter suspicious query string
- Updated .pot file
- Simplified Chinese by æµ·æ»¨
- Persian by Ibrahim Jafari
- Typo correction by ihuston
- Fixed Bit51 Google+ Link
- Better proxy support for ban users by kalvindukes
- Updated Spanish translation by Pablo Romero
- Updated Readme
- Updated .pot file
- Fixed error message that could appear when creating backups
- Correct Changelog not displaying correctly on WordPress.org after version 3.5.1
- Replaced Turkish language version lost in when tagging 3.5 in the WordPress.org repository
- Solved a conflict with other Bit51 plugins that use the common Bit51 class
- Integrate with Foo Plugins support system
- Fixed role translation call for Strong password enforcement
- Turkish by Hakan Er
- Random version number no longer strips unrelated GET variables for better compatibility
- Upgrading no longer automatically rewrites .htaccess and wp-config resulting in much improved reliability
- Fixed possible error when login fails and PHP is set to report errors to screen
- Replaced feed with standard WordPress feed
- Added better error checking for feed should Feedburner (or any other provider) kill it again
- More secure user query thanks to John Cave
- Greatly improved intl date handling by SCUDELLER Eric
- Added: French translation by SCUDELLER Eric
- Fixed: bug preventing Jetpack’s Infinite Scroll from working with long URL protection
- Fixed error message that may occur if InfiniteWP is not installed.
- Added compatibility with InfiniteWP (http://infinitewp.com/)
- Updated default ban list as it was a little too restrictive for my taste
- Added export of 404 logs in .csv format (experimental)
- Add X-Forwarded-For ability to IP logging
- Minor bug and typo fixes
- Updated usability on ban lists
- Ban list threshold now triggered on hit and not 1 after
- Replace database override of awaymode with wp-config constant
- Filecheck override is now done through wp-config constant
- Added option to generate new secret key in hide backend
- Added Slovak translation by Erich SzabÃ³
- Possible Google Maps fix for Apache
- Improved time handling for away mode, lockouts, logs, and more
- Added Tagalog translation by Hanne of â€‹http://pointen.dk/
- Various table updates from Michael Conover (@sidtheduck) at sidtheduck.com.
- Load plugin as global to reduce multiple executions
- Fixed rewrite rules for banned hosts
- Updated .pot file
- Other minor bugfixes and refactoring
- fixed input vulnerability found at http://packetstormsecurity.org/files/116317/ithemes-security-3.4.3-Cross-Site-Scripting.html
- fixed email address in footer information on backup screen
- file check exclusions should now work properly for individual files.
- One-click protection is now part of the install script.
- Won’t log or even check 404 if feature is off.
- Don’t clear cache during away check. Let’s see instead if the transients â€¦
- Don’t clear Supercache page cache on clear logs
- Only clear WP Supercachce when full page cache clearing is required
- Gravatars will no longer dissappear after changing user 1 id
- Better cache clearing when changing options
- Reworked away mode for better cache handling
- Subdirectory redirects should now work
- Fixed error message on logout
- Fixed password reset email link
- Will no longer duplicate IPs in ban list when entered via auto-ban
- Minor style updates
- Better namespacing in content.php
- Removed 126.96.36.199/8 from hackrepair.com blacklist
- remove yandex from hackrepair.com blacklist
- Clean all logs when checked
- Better logic for SSL checking
- Removed echo statement in Filecheck
- Highly compressed NGINX rules
- Added to «Filter Suspicious Query String» Logic
- Added Russian Translation
- Updated Hindi contributor to Outshine Solutions
- Prevented file change warning from displaying to non-admins
- Fixed error causing multiple backup emails
- Added ability to change ID of user with ID 1
- Fixed bug in plugin base url
- Added extra warnings and «escape route» for away mode
- Fixed hide backend issues since WordPress 3.4
- Lookup IP addresses directly from logs
- Fixed dbdelta errors on upgrade
- Updated form styles and appearance
- Added tabs to settings pages for increased usability
- Duplicate IP addresses won’t be saved to banned list
- Wildcards now correctly save to banned list
- Suppress errors on filecheck arrays
- Fixed link to permalink settings in hide backend
- Added extra save buttons to system tweaks
- Added logging memory usage to filecheck
- Updated readme.txt
- Updated .pot
- More checks to ensure blank «Deny from» lines don’t appear in .htaccess
- Added host and user agent blacklist by HackRepair.com
- Changed «Options All -Indexes» to «Options -Indexes» in .htaccess rules
- Added log view for all bad login attempts to view logs
- Always show .htaccess and wp-config.php changes in Dashboard
- Database backups no longer turn on automatically with one-click secure.
- Replaced unique key in database tables with primary key (tested in 3.4)
- Hindi translation by Outshine Solutions
- Spanish translation by Pablo Romero
- Lithuanian translation by Vincent G
- Fixed bug that could allow blank hosts in .htaccess for ban users
- Removed obsolete translations from before version 3.0
- Fixed various typos
- Numerous minor bug fixes
- Support moved back to WordPress.org forums
- Users can now specify email address for database backups
- Fixed bug throwing error when saving changes to existing users
- Corrected typo in intl hook
- List banned IPs on separate lines for readability
- Replaced all instances of WordPress with WordPress
- Logs no longer show errors when records are cleared while viewing file change details
- File check will no longer automatically enable on servers with low RAM
- An extra database key has been introduced to easily disable file checking if it causes memory errors
- updated .pot
- Sanitize ALL server variables to prevent XSS vulnerability
- Added configurable email address for all email notifications
- Added ability to turn off dashboard warning for file check
- Password reset form will now require strong passwords if configured
- Ability to automatically blacklist an IP address after a specified number of lockouts
- Various minor bugfixes
- Turning off front-end ssl will stop ssl redirect loops in sites with an existing ssl implementation
- Updated language and explanations for various features
- Updated .pot
- Fixed date offset in log views
- Fixed site admin renaming for multisite users
- Fixed typos throughout
- Block concat MySQL command
- Deny access to readme.txt in protect files
- Fixed 404 table description
- Added domain name to email notifications
- Improved folder check login
- Suppress error messages for file-check operations
- Fixed 500 error when ban-users in enabled and IP or agents list are empty
- Fixed error that logged bad logins and 404s even when features were turned off
- Added choice to completely disable front-end SSL, enable per page, or enable site-wide
- Fixed login URL on new user email when new user is created by an existing user and hide backend is enabled
- Default all SSL to off for new installations
- Fixed strong password roles to work correctly
- A little 418 humor
- Updated .pot file
- Updated readme.txt
- File checker checks for changed files
- SSL for individual pages and posts
- One-click protection removes all .htaccess and wp-config.php options
- Option to not allow the plugin to write to .htaccess and wp-config.php
- Tweaked NGINX rewrite rules
- Moved SSL options to separate page for better usability
- Tables now display in native WordPress format
- Updated language throughout
- Tweaked Apache rewrite rules
- Various minor bug-fixes
- New installation video (see plugin homepage)
- Updated .pot file
- Significantly less resource usage
- Fixed white screen errors on load
- Fixed backup scheduling errors
- updated .pot file
- numerous minor bugfixes
- Displays log messages for all lockouts
- Scheduled backup times can be much more easily customized
- Setting wp-config.php and .htaccess to 0444 is now optional
- Updated .pot file
- Fixes to Apache/LiteSpeed rules and NGINX rules
- Numerous minor bugfixes
- Fixed bug with redundant backup caller in admin script
- Better LiteSpeed support
- Better database backup scheduling
- Better line spacing in .htaccess and wp-config.php
- WordPress 3.3.1 now required
- Status area now links to proper options and not top of tweaks page
- NGINX rule fixes
- admin-ajax.php now works even with hide backend
- error surpression on file operations
- update .pot
- Many language updates
- Better update script for multisite installs
- Fixed multi-site issue due to 3.0.8 update support fix
- Fixed awaymode settings issues
- Fixed improper php open tags
- Fixed erroneous PHP_EOL in nginx rules
- LiteSpeed support
- Better update support (not relying on activation hook anymore)
- Added abstract keyword to bit51.php
- Removed itsec references in bit51.php
- updated .pot file
- Changed method of end of line character technique for better cross-platform server compatibility
- Fixed 2 lines of <? in content.php replacing them with <?php
- Another fix to the «line 2072» error. This would be a lot easier with a Windows host as those are the only folks that seem to have the issue
- Changes to language on ban users page
- fixed «line 2072» error
- Changed IP banning to only accept * wildcards for ranges
- All host banning is not done via server configuration rather than php
- Numerous minor bugfixes
- Fixed bug in backup file path
- Fixed default options on saving
- Fixed setup options
- Other minor bugfixes
- Turned off flag that caused plugin settings to reset on update.
- Complete rewrite from the ground up
- Menu changes
- UI completely rewritten
- Now supports NGINX
- Scheduled database backups
- Added ability to block user agents in addition to hosts
- Numerous bugfixes
- Another attempt to fix the login error that started with 2.16. Changed logic for determining hide backend feature.
- Fixed an error that started with version 2.16 and prevented user from being able to login to the WordPress Dashboard.
- Fixed login link in new user email after breaking it in version 2.15
- Now loads all features at init to [hopefully] eliminate function not found errors
- Bugfixes from 2.13
- Removed randomized version for all logged-in users due to conflicts with admin-bar
- Bugfixes from 2.12
- Bugfixes from 2.11
- Fixed login-slug in new user email
- Fixed login slugs throughout site
- Remove reset-password options
- Improved rewrite rules (I would credit the author but I’m afraid in a bone headed move I never wrote down the author with the notes)
- No longer loads pluggable
- Added Romanian translation by Luke Tyler
- readme.txt typo correction
- Added ability to whitelist hosts and ip addresses for intrusion detection
- intrusion detection now lists 404 errors found to help ease troubleshooting
- intrusion detection now records referrer to make tracking 404 errors easier
- corrected error when attempting to list multiple hosts when banning users
- German Translation by Stefan Meier
- Fixed a logic bug caused by changes in 2.7
- Fixed a bug preventing login lockouts from releasing.
- Added link to author of Italian Translation
- Fixed bug preventing the «Ban Users» function from working.
- Italian translation by Paolo Stivanin
- Support information moved to separate page for easy access
- Minor bug fixes
- Fixed a bug that generated a 404 error when clicking the reset password link that is emailed to users
- Added the option to customize the error message displayed for the login lockdown and intrusion detection lockouts
- Fixed various typos
- meta.php require_once now works correctly
- fixed bug in which .htaccess and wp-config.php were not reporting correct permissions
- Version is now hidden on admin pages except for multi-site
- Emergency fix restoring version number display for backend as previous fix made multi-site installations unusable
- Added options to customize intrusion detection to allow custom lockout duration and error threshold
- Time now correctly displays for intrusion detection lockouts and lockouts are released at the correct time
- Version number now hidden for all users without administrator role on backend
- Saved hide backend key to database to allow for easier use in other plugins that link directly to wp-login.php (still has to be manually entered in each affected plugin)
- Will now use the correct wp-config.php file if it is located outside of the directory used for the wordpress installation
- Empties APC cache (when installed) after changing wp-content directory preventing the necessity to restart Apache
- Fixed display bugs for login and intrusion lockout lists.
- Now supported by Bit51.com
- Removed blocking of http HEAD requests to improve integration with social networking APIs such as Twitter
- French translation by Claude ALTAYRAC
- Error message on lockouts more ambiguous
- Added email notification for intrusion detection lockouts
- Added Bahasa Indonesia (Indonesian) translation by Belajar SEO, Jasa SEO Indonesia
- Minor bug fixes
- Changed plugin description
- Improved translation support
- Added Turn off file editor in WordPress backend
- Improved accuracy of version checking when upgrading
- Ban Users now allows for more than just IP address, it has been renamed accordingly
- Renamed detect 404s section to intrusion detection to include upcoming features
- general spelling and grammer corrections
- Moved configuration to network dashboard for multisite installations
- Improved multisite support
- Warns if .htaccess or wp-config.php files aren’t writable where needed
- Added icon to menu for easier identification
- Cleaned up and refined status information
- Fixed WLManifest link removal from header
- Added nofollow to all meta links
- «Away Mode» page now displays current time even when feature has not been enabled
- Status page now shows system information
- htaccess contents moved to status page
- fixed fatal activation error affecting php 5.2 users
- Meta links update correctly when changing backend links
- Fixed another issue that prevented the «htaccess» options page from displaying on some hosts
- Fixed an issue that prevented the «htaccess» options page from displaying on some hosts
- Finished support for localization
- Fixed bug that prevented cleaning old lockouts from database
- More code documentation
- Added warnings to changing content directory (until I can find a good way to update all existing content)
- Added options to clean old entries out of the database
- Fixed minor typos throughout
- Updated Homepage
- Fixed error for potential conflicts with old htaccess rules
- Removed hotlinking protection as it has been deemed to be outside the scope of this project
- Removed protocol from hide backend htaccess rules for consistency between http and https
- Combined all httaccess rules into single iThemes Security Block
- 404 check now ignores all logged in users
Fixed a bug that could erase part of the wp-config file= 0.12.BETA =
Changing content directories should no longer break sites that were upgraded from versions prior to 3.0
- Update to project homepage and other minor changes
- Removed WP version check from status page as it was redundant
- On uninstall wp-content location will be returned to default
- Fixed setup error
- Error checking now correctly identifies database table prefix
- Rendom version # generator now removes version number from scripts and css where it can (thanks to Dave for this)
- Bug fixes
- Internationalization improvements
- Fixed more critical bugs
- Fixed more critical bugs
- Fixed 2 critical bugs
- Major refactoring
- Streamline database tables
- Numerous bugfixes
- Code documentation and continued internationalization prep
- Changed the main menu name to «Security»
- Minimum requirement raised to 3.0.2
- Begun code documentation and intl prep
- Numerous bugfixes
- 404 check will NOT ban logged in users
- Lockdown rules no longer apply to logged in users
- Updated hidebe to handle standard logout links
- Numerous other bugfixes
- Finished status reporting
- Force SSL for admin pages (on supporting servers)
- Change wp-content path
- Added security checklist
- Added option to rename existing admin account
- Added option to change DB table prefix
- Various bugfixes
- Added more htaccess security options
- All htaccess options have been moved to their own page
- Added simple intrusion detection based on 404s
- Bugfixes and code optimization
- Deactivating now removes all htaccess areas and turns off associated options
- Enforce strong passwords for all users of a given minimum role
- Minor bug fixes
- Added various .htaccess options to strengthen file security
- Modified «hide backend» rewrite rules to work with multi-site
- Removed non-security hide-backend options
- Various bug fixes
- Renamed «General» options page to «System Tweaks» to avoid confusion
- Added more options to clean up WordPress headers
- Added options to remove plugin notifications from non-super admin users
- Continued code refactoring and bug-fixes
- Improved error handling and upgrade support
- Combined status and support options pages
- Added sanitization and validation to user input
- Added «away mode» to limit backend access by time
- Script no longer dies when logged out and instead returns to homepage.
- Complete refactor of the existing code
- Divided settings sections for better UX
- Added htaccess checks
- Redesigned options system for less database calls
- Reduced table usage from 4 to 2
- Added email notifications for login limiter
- Added complete access blocker for login limiter
- Added login limiter to limit invalid attempts
- various Bug fixes
- Corrected error display
- Added registration rules regardless of whether registrations are on or off.
- Added «Display random version to non-admins»
- Fixed rewrite rules on hide admin urls so going to the admin slug will work whether the user is logged in or not
- Added crude upgrade warning to warn of old (not so great) rewrite rules
- Optimized and commented code
- Added uninstall function
- Numerous fixes to bugs and logic
- First alpha release including simple feature set.