All In One WP Security & Firewall

Beschreibung

EIN UMFASSENDES, EINFACH ZU BEDIENENDES, STABILES UND GUT UNTERSTÜTZTES WordPress-SICHERHEITS-PLUGIN

WordPress selbst ist eine sehr sichere Plattform. Es hilft jedoch, deiner Website zusätzliche Sicherheit und eine Firewall hinzuzufügen, indem du ein Sicherheits-Plugin verwendest, das viele gute Sicherheitsmaßnahmen durchsetzt.

Das All-in-One-WordPress-Security-Plugin bringt deine Website-Sicherheit auf eine ganz neue Ebene.

Dieses Plugin wurde von Experten entworfen und geschrieben und ist einfach zu bedienen und zu verstehen.

Es reduziert das Sicherheitsrisiko, indem es auf Schwachstellen überprüft und die neuesten empfohlenen WordPress-Sicherheitsverfahren und -techniken implementiert und durchsetzt.

All In One WP Security verwendet auch ein beispielloses Sicherheitspunkte-Bewertungssystem, um zu messen, wie gut du deine Website basierend auf den von dir aktivierten Sicherheitsfunktionen schützt.

Unsere Sicherheits- und Firewall-Regeln sind in die Kategorien „Basic“, „Intermediär“ und „Fortgeschritten“ unterteilt. Auf diese Weise kannst du die Firewall-Regeln schrittweise anwenden, ohne die Funktionalität deiner Website zu beeinträchtigen.

Das All-In-One-WordPress-Security-Plugin verlangsamt deine Website nicht und es ist 100 % kostenlos.

Besuche die Seite WordPress Security Plugin (engl.) für weitere Details.

Nachfolgend findest du eine Liste der Sicherheits- und Firewall-Funktionen, die in diesem Plugin angeboten werden:

Benutzerkonten-Sicherheit

  • Erkenne, ob es ein Benutzerkonto mit dem Standard-Benutzernamen „admin“ gibt, und ändern den Benutzernamen einfach in einen Wert deiner Wahl.
  • Das Plugin erkennt auch, ob du WordPress-Benutzerkonten hast, die identische Anmelde- und Anzeigenamen verwenden. Es ist eine schlechte Sicherheitspraxis, ein Konto zu haben, bei dem der Anzeigename mit dem Anmeldenamen identisch ist, denn du machst es Hackern 50 % leichter, weil sie den Anmelde-Namen bereits kennen.
  • Passwortstärke-Tool, mit dem du sehr sichere Passwörter erstellen kannst.
  • Stoppe die Enumeration der Benutzer. So können Benutzer/Bots keine Benutzerinformationen über den Permalink des Autors entdecken.

Benutzeranmelde-Sicherheit

  • Schütze dich vor „Brute-Force Anmelde-Angriffe“ mit der Anmelde-Sperrfunktion. Benutzer mit einer bestimmten IP-Adresse oder einem bestimmten IP-Bereich werden für eine bestimmte Zeitspanne, basierend auf den Konfigurationseinstellungen, aus dem System ausgeschlossen und du kannst dich auch für eine Benachrichtigung
    per E-Mail entscheiden, wenn jemand wegen zu vieler Anmeldeversuche gesperrt wird.

  • Als Administrator kannst du eine Liste aller gesperrten Benutzer einsehen. Sie werden in einer leicht lesbaren und navigierbaren Tabelle angezeigt. Diese ermöglicht es dir auch, einzelne oder mehrere IP-Adressen per Button-Druck freizuschalten.

  • Ausloggen aller Benutzer nach einem konfigurierbaren Zeitraum erzwingen
  • Überwachen/, zeige fehlgeschlagener Anmeldeversuche an. Die IP-Adresse des Benutzers, die Benutzer-ID/Benutzername und Datum/Uhrzeit des fehlgeschlagenen Anmeldeversuchs werden angezeigt.

  • Überwache/, zeige die Kontoaktivität aller Benutzerkonten auf deinem System an, indem du den Benutzernamen, die IP-Adresse, Datum/Uhrzeit der Anmeldung und Datum/Uhrzeit der Abmeldung im Auge behältst.

  • Möglichkeit, IP-Adressbereiche, die versuchen, sich mit einem ungültigen Benutzernamen anzumelden, automatisch zu sperren.
  • Möglichkeit, eine Liste aller Benutzer anzuzeigen, die derzeit bei deiner Website angemeldet sind.
  • Ermöglicht es dir, eine oder mehrere IP-Adressen in einer speziellen Whitelist anzugeben. Die auf der Whitelist aufgeführten IP-Adressen haben Zugriff auf deine WP-Anmelde-Seite.
  • Füge ein Google-reCaptcha oder ein einfaches Mathematik-Captcha zum WordPress-Anmeldeformular hinzu.
  • Füge Google-reCaptcha oder ein einfaches mathematisches Captcha zum Formular für vergessene Passwörter in deinem WP-Anmeldesystem hinzu.

Benutzer-Registrierungs-Sicherheit

  • Manuelle Genehmigung von WordPress-Benutzerkonten aktivieren. Wenn deine Website es Leuten erlaubt, ihre eigenen Konten über das WordPress-Registrierungsformular zu erstellen, dann kannst du SPAM- oder gefälschte Registrierungen minimieren, indem du jede Registrierung manuell genehmigst.
  • Die Möglichkeit, Google-reCaptcha oder ein einfaches Mathematik-Captcha zur WordPress-Benutzerregistrierungsseite hinzuzufügen, um dich vor der Registrierung von Spam-Benutzern zu schützen.
  • Die Möglichkeit, einen Honeypot zum Benutzerregistrierungsformular von WordPress hinzuzufügen, um Registrierungsversuche durch Robotern zu reduzieren.

Datenbank-Sicherheit

  • Mit einem Klick auf einen Button kannst du das Standard-WP-Präfix einfach auf einen Wert deiner Wahl einstellen.
  • Plane automatische Backups und E-Mail-Benachrichtigungen oder erstelle mit einem Klick ein sofortiges DB-Backup, wann immer du willst.

Dateisystem-Sicherheit

  • Identifiziere Dateien oder Ordner, die Berechtigungseinstellungen haben, die nicht sicher sind, und setze die Berechtigungen mit einem Klick auf einen Button auf die empfohlenen sicheren Werte.
  • Schütze deinen PHP-Code, indem du die Dateibearbeitung im WordPress-Administrationsbereich deaktivierst.
  • Sieh und überwache alle Protokolle des Hostsystems auf einer einzigen Menüseite und bleibe über alle Probleme auf deinem Server auf dem Laufenden, damit du sie schnell bearbeiten kannst.
  • Verhindere, dass Personen auf die Dateien readme.html, license.txt und wp-config-sample.php deiner WordPress-Website zugreifen.

htaccess und wp-config.php-Dateisicherung und Wiederherstellung

  • Sichere einfach deine originalen .htaccess- und wp-config.php-Dateien, falls du sie verwenden musst, um defekte Funktionalitäten wiederherzustellen.
  • Änder den Inhalt der aktuell aktiven .htaccess- oder wp-config.php-Dateien aus dem Admin Dashboard mit wenigen Klicks.

Schwarze Listenfunktionalität

  • Sperre Benutzer durch Angabe von IP-Adressen oder verwende eine Wildcard, um IP-Bereiche anzugeben.
  • Sperre Benutzer, indem du bestimmte Benutzer-Agents angibst.

Firewall-Funktionalität

Dieses Plugin ermöglicht es dir, deiner Website über die htaccess-Datei einfach eine Menge Firewall-Schutz hinzuzufügen. Eine htaccess-Datei wird von deinem Webserver vor jedem anderen Code auf deiner Website verarbeitet.
Diese Firewall-Regeln stoppen also bösartige Skripte, bevor sie die Chance erhalten, den WordPress-Code auf deiner Website zu erreichen.

  • Zugangskontrolleinrichtung.
  • Aktiviere sofort eine Auswahl von Firewall-Einstellungen, die von einfach, mittel bis fortgeschritten reichen.
  • Aktiviere die berühmten Firewall-Regeln der „6G Blacklist“ mit freundlicher Genehmigung von Perishable Press
  • Verbiete Kommentar-Beiträge über Proxys.
  • Blockiere den Zugriff auf die Debug-Protokolldatei.
  • Trace und track deaktivieren.
  • Verweigere schlechte oder bösartige Abfragezeichenfolgen.
  • Schütze dich vor Cross-Site-Scripting (XSS), indem du den umfangreichen erweiterten Zeichenfolgenfilter aktivierst.
    Oder bösartige Bots, die kein spezielles Cookie in ihrem Browser haben. Du (der Website-Administrator) wirst wissen, wie man dieses spezielle Cookie setzt und kannst dich bei deiner Website anmelden.
  • WordPress-PingBack-Schwachstellenschutz-Funktion. Diese Firewall-Funktion ermöglicht es dem Benutzer, den Zugriff auf die Datei xmlrpc.php zu verbieten, um sich vor bestimmten Schwachstellen in der Pingback-Funktion zu schützen. Dies ist auch hilfreich, um zu verhindern, dass Bots ständig auf die Datei xmlrpc.php zugreifen und die Serverressource verschwenden.
  • Möglichkeit, vorgebliche Googlebots daran zu hindern, deine Website zu durchsuchen.
  • Möglichkeit, das Hotlinking von Bildern zu verhindern. Verwende dies, um zu verhindern, dass andere Personen deine Bilder direkt verlinken.
  • Möglichkeit, alle 404 Ereignisse auf deiner Website zu protokollieren. Du kannst auch wählen, ob IP-Adressen, die zu viele 404er produzieren, automatisch gesperrt werden sollen.
  • Möglichkeit, individuelle Regeln hinzuzufügen, um den Zugriff auf verschiedene Ressourcen deiner Website zu blockieren.

Brute-Force-Anmelde-Angriffs-Prävention

  • Blockiere Brute-Force Anmelde-Angriffe sofort über unsere spezielle Cookie-basierte Brute-Force Anmelde-Schutz-Funktion. Diese Firewall-Funktionalität blockiert alle Anmeldeversuche von Personen und Bots.
  • Möglichkeit, dem WordPress-Anmeldeformular ein einfaches mathematisches Captcha hinzuzufügen, um gegen Brute-Force-Anmeldeangriffe zu kämpfen.
  • Möglichkeit, die Anmelde-Seite des Administrators auszublenden. Benenne deine WordPress Anmelde-Seiten-URL um, sodass Bots und Hacker nicht auf deine echte WordPress-Anmelde-URL zugreifen können. Mit dieser Funktion kannst du die Standard-Anmeldeseite (wp-login.php) auf etwas ändern, das du konfigurierst.
  • Möglichkeit, den Login-Honeypot zu verwenden, was dazu beiträgt, Brute-Force-Anmelde-Versuche von Robotern zu reduzieren.

Sicherheits-Scanner

  • Der Scanner zur Erkennung von Dateiänderungen kann dich warnen, wenn sich Dateien in deinem WordPress-System geändert haben. Du kannst dann untersuchen und sehen, ob es sich um eine legitime Änderung oder um die Injektion eines unzulässigen Codes handelt.

Kommentar-Spam-Sicherheit

  • Überwache die aktivsten IP-Adressen, die dauerhaft die meisten SPAM-Kommentare produzieren und blockiere diese sofort mit einem Button-Klick.
  • Verhindere, dass Kommentare gesendet werden, wenn sie nicht von deiner Domain stammen (dies sollte einige Spam-Bot-Kommentarbeiträge auf deiner Website reduzieren).
  • Füge dem WordPress-Kommentar-Formular ein Captcha hinzu, um Sicherheit vor Spam-Kommentaren hinzuzufügen.
  • IP-Adressen automatisch und dauerhaft blockieren, die eine bestimmte Anzahl von Kommentaren überschritten haben, die als SPAM gekennzeichnet wurden.

Front-End-Textkopierschutz

  • Möglichkeit, den Rechtsklick, die Textauswahl und die Kopieroption für dein Frontend zu deaktivieren.

Regelmäßige Updates und Ergänzungen neuer Sicherheitsfunktionen

  • WordPress-Security ist etwas, das sich im Laufe der Zeit weiterentwickelt. Wir werden das All-In-One-WP-Security -Plugin regelmäßig mit neuen Sicherheitsfunktionen (und ggf. Korrekturen) aktualisieren, damit du sicher sein kannst, dass deine Website auf dem neuesten Stand der Sicherheitstechniken sein wird.

Funktioniert mit den populärsten WordPress-Plugins

  • Es sollte reibungslos mit den meisten populären WordPress-Plugins funktionieren.

Zusätzliche Funktionen

  • Möglichkeit, die WordPress-Generator-Meta-Informationen aus der HTML-Quelle deiner Website zu entfernen.
  • Die Möglichkeit, die WordPress-Versionsinformationen aus den JS- und CSS-Dateiincludes deiner Website zu entfernen.
  • Möglichkeit, Personen daran zu hindern, auf die Dateien readme.html, license.txt und wp-config-sample.php zuzugreifen
  • Möglichkeit, das Frontend deiner Website vorübergehend für allgemeine Besucher zu sperren, während du verschiedene Backend-Aufgaben erledigst (Sicherheitsangriffe untersuchen, Website-Upgrades durchführen, Wartungsarbeiten durchführen usw.).
  • Möglichkeit zum Export/Import der Sicherheitseinstellungen.
  • Verhindere, dass andere Websites deine Inhalte über einen Frame oder ein Iframe anzeigen.

Plugin-Support

  • Wenn du eine Frage oder ein Problem mit dem All-In-One-Security-Plugin hast, poste es im Support-Forum und wir werden dir helfen.

Entwickler

  • Wenn du ein Entwickler bist und einige zusätzliche Hooks oder Filter für dieses Plugin brauchst, dann lass es uns wissen.
  • Github-Repository – https://github.com/Arsenal21/all-in-one-wordpress-security

Übersetzungen

  • Das All-In-One-WP-Security-Plugin kann in jede Sprache übersetzt werden.

Aktuell verfügbare Übersetzungen:

  • Englisch
  • Deutsch
  • Spanisch
  • Französisch
  • Ungarisch
  • Italienisch
  • Schwedisch
  • Russisch
  • Chinesisch
  • Portugiesisch (Brasilien)
  • Persisch

Besuche die Seite WordPress Security Plugin (engl.) für weitere Details.

Datenschutzerklärung

Dieses Plugin kann IP-Adressen aus Sicherheitsgründen sammeln, wie z.B. zur Abwehr von Brute-Force-Anmeldebedrohungen und bösartigen Aktivitäten.
Die gesammelten Informationen werden auf deinem Server gespeichert. Es werden keine Informationen an Dritte oder entfernte Serverstandorte übermittelt.

Benutzung

Gehe nach der Aktivierung des Plugins in das Einstellungsmenü und folge den Anweisungen.

Installation

Um damit zu beginnen deine WordPress-Website sicherer zu machen:

  1. Lade die Datei „all-in-one-wp-security.zip“ von der Seite Plugins-> Installieren-> Plugin hochladen im WordPress-Dashboard hoch.
  2. Aktiviere das Plugin mittels des „Plugins“-Menüs in WordPress
  3. Gehe zum Menü Einstellungen unter „WP-Security“ und beginne mit der Aktivierung der Sicherheitsfunktionen des Plugins.

FAQ

Überprüfe die folgende Seite für F.A.Q (Häufig gestellte Fragen, siehe den Abschnitt FAQ):
https://www.tipsandtricks-hq.com/wordpress-security-and-firewall-plugin

Rezensionen

14. November 2019
The developers of this fine piece of software restore my faith in mankind. This software, along with a well coordinated and a proper server management, is enough to keep your wordpress sites secure. I don't have enough words to thank you. It's just what every wordpress site should have.
4. November 2019
This really is an excellent plugin, in fact out of all the dozens or hundreds of plugins I've used, this is probably my favourite, all things considered. Very effective, yet easy to use - in other words makes me look clever to my colleagues! 🙂
27. Oktober 2019
If you use the "Maintenance" mode, you can't log back in again. Even though the admin page. You have to disable the plugin via FTP to login and disable the Maintenance Mode. It needs a login box for admins. Damn stupid design.
Lies alle 914 Rezensionen

Mitwirkende & Entwickler

„All In One WP Security & Firewall“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin mitgewirkt:

Mitwirkende

„All In One WP Security & Firewall“ wurde in 9 Sprachen übersetzt. Danke an die Übersetzerinnen und Übersetzer für ihre Mitwirkung.

Übersetze „All In One WP Security & Firewall“ in deine Sprache.

Interessiert an der Entwicklung?

Durchstöbere den Code, sieh dir das SVN Repository an oder abonniere das Entwicklungsprotokoll per RSS.

Änderungsprotokoll

4.4.2

  • Die Schwachstelle im Zusammenhang mit der offenen Umleitung und der Offenlegung der versteckten Anmeldeseite für den speziellen Einzelfall wurde behoben. (Danke an Erwan (wpscanteam), dass er uns informiert hat)

4.4.1

  • Es wurde ein Fehler behoben, bei dem Apache-Anweisungen nach der Reaktivierung des Plugins nicht wieder in die .htaccess-Datei eingefügt wurden.
  • Es wurde ein Fehler behoben, der damit zusammenhing, dass das Abmeldedatum für die Kontoaktivität nicht festgelegt wurde.

4.4.0

  • Zusätzliche Robustheit bei der Anmeldeverriegelung durch Ersetzen der strtotime-Funktion durch DateTime/DateInterval.
    Dies sollte verhindern, dass 32-Bit-Systeme auf das maximale Datum vom 19. Januar 2038 beschränkt werden.
  • Fehler im Zusammenhang mit Captcha-Funktionen behoben.
  • Die Funktionalität „Angemeldete Benutzer“ für Multisite wurde korrigiert und verbessert.
  • Setze immer gültige Daten, um Fehler zu vermeiden, wenn der strenge Modus auf mysql aktiviert ist. Danke an Davide.

4.3.9.4

  • Removed whois feature because it adds relatively little value and the third-party library used is not being maintained regularly.
  • Fixed „headers already sent“ error when bulk action performed using aiowps list table.

4.3.9.3

  • Fixed another captcha bug related to comment form.

4.3.9.2

  • Fixed various captcha bugs: woocommerce lost password page, custom login form page, etc

4.3.9.1

  • Fixed rename login page feature bug introduced after WP core change in version 5.2.

4.3.9

  • Fixed captcha bug.
  • Fixed PHP_EOL issue where some IPv6 and v4 addresses saved in settings were incorrectly deemed invalid.
  • Tightened file permission for wp-config.php to „640“
  • Fixed DB prefix change bug for cases where DB had tables of type „view“.
  • Fixed some translation string issues.
  • Minor style fix for wp list table pagination nav buttons.

4.3.8.3

  • Trying again – Fixed login captcha authentication bug.

4.3.8.2

  • Fixed login captcha authentication bug.

4.3.8.1

  • Minor bug fix – added missing check to enqueue recaptcha script only if that feature is enabled.

4.3.8

  • Added ability to hide secret rename login page link when sending emails to people asking for personal data export.
  • Fixed Google reCaptcha not showing on comment page.
  • Fixed activation handler and creation of DB tables to handle multi-site activations more robustly.
  • Improved reCaptcha code to prevent the occasional occurrence of „Uncaught Error: reCAPTCHA placeholder element must be an element or id“ error.
  • Added extra check for PHP_OS value to prevent Apple „DARWIN“ being interpreted as windows server.
  • Corrected some minor translation issues on rename login page.
  • Increased priority of authenticate hook for captcha check.
  • Updated the Dutch Language file.

4.3.7.2

  • More „get_home_path“ fatal error preventions.

4.3.7.1

  • Fixed fatal error regarding „get_home_path“ function.

4.3.7

  • Added Google reCaptcha feature for login forms.
  • Improved code which checks if site is main for multi-site installations.
  • Removed the text domain string from the translation functions in the wp-security-rename-login-feature.php file.
  • Changed .htaccess path location to use get_home_path().
  • Fixed minor woocommerce captcha bug

4.3.6

  • Added new tab called „WP REST API“ in the Miscellaneous menu and created separate feature which disables unauthorized REST access for non-logged in users independent of the users enumeration feature.
  • Improved dashboard page widget area display.
  • Small translation string fix in the rename login page feature.

4.3.5

  • Fix – Error: Call to undefined function the_privacy_policy_link() in older versions of WordPress.
  • Added a check to disable file change detection feature and prevent fatal errors when FilesystemIterator is not available due to old versions of PHP.
  • Improved get_login_fail_count method in the AIOWPSecurity_User_Login class which will fix cases where login lockdown
    was not working on some servers due to timestamp difference between PHP current_time( ‚mysql‘ ) and mysql now().

4.3.4

  • Modified rename login page to handle GDPR Export/Erase Personal Data request.
  • Fixed woocommerce registration page captcha bug.
  • Improved users enumeration so that authenticated requests to the REST API are allowed but others are blocked.
  • Improved logic in Renamed Login Page settings such that unnecessary call of AIOWPSecurity_Utility_Htaccess::write_to_htaccess() function is avoided.

4.3.3.1

  • Fixed a typo with the newly added action hook – aiowps_before_wp_die_renamed_login

4.3.3

  • Fixed bug – aiowps will now allow access to admin-post.php from front-end when rename login feature is active.
  • Modified login lockdown feature so that the exact IP address is locked down and not the IP range.
  • Added new filter (aiowps_ip_blocked_output_page) which allows user to filter the complete output when someone’s IP has been locked out.
  • Added new action hook (aiopws_before_wp_die_renamed_login) for the renamed login feature which fires just before the wp_die event which produces the „Not available“ behaviour.
  • Removed unused code.
  • Modified get_user_ip_address to get the first IP address in cases where there are multiple comma separated addresses provided – example X-Forwarded-For.

4.3.2

  • Added new IP address settings page which user the ability to configure which $_SERVER global the IP address will be retrieved from. (New setting found in WP Security >> Settings >> Advanced Settings)
  • Fixed bug in .htaccess rules caused when 6G and IP blacklist firewall rules were simultaneously enabled.
  • Fixed bug where captcha answer was being ignored on woocommerce login page.
  • Added support for unlock requests made from woocomerce account login page when rename login feature is active.
  • Added useful debug code for troubleshooting in the fake googlebot function.
  • Some general code cleanup and improvement.
  • Added code to prevent direct access data leaks.
  • Added captcha settings for BBPress new topic form.
  • Fixed minor bug in dashboard page when checking if htaccess rules applied.
  • Added a check for Windows server installation in File Permissions feature – this feature is not applicable for Windows servers.
  • Added check to display comment captcha only when user not logged in.

4.3.1

  • Improved white list directives to cater for Apache 2.4 and earlier versions.
  • Added 3 filters for the manual account registration approval email: aiowps_register_approval_email_subject, aiowps_register_approval_email_msg, aiowps_register_approval_email_from_name
  • Added configuration option to allow custom firewall rules to be applied at beginning of all rules applied by aiowps.
  • Changed record insertions to DB table aiowps_failed_logins to store the full IP address instead of IP range.

4.3.0

  • Updated wp-security-rename-login-feature.php to include latest WordPress core changes.
  • Added captcha for woocommerce login and registration forms.
  • Fixed „mixed line endings“ warnings for whois library.
  • Moved DB cleanup task cron job from daily to hourly.
  • Updated the reapply htaccess function so it doesn’t create the header already sent error.

4.2.9

  • Changed the parameter in current_user_can function to use an administrator capability instead of the „administrator“ role name.
  • Added some new hooks to the AIOWPSecurity_WP_Loaded_Tasks called aiowps_wp_loaded_tasks_start and aiowps_wp_loaded_tasks_end.
  • Improved get_locked_ips() function and added $wpdb->prepare statement.
  • Added more missing translation domain parameters for translatable strings in the rename login page.
  • Deleted local copy of the Persian and Italian language files. These translations are available on translate.wordpress.org.
  • Domain path and text domain added to plugin header.
  • Changed the get_user_ip_address functions so that $_SERVER[‚REMOTE_ADDR‘] is the primary method used to obtain IP address.
  • Added enumeration block via REST API (wp >= 4.7)

4.2.8

  • Improved „User Registration“ feature to bypass the pending approval status for new users created in admin side.
  • Fehler in der Whois-Bibliothek behoben.
  • Parameter für die Übersetzungsdomäne für übersetzbare Zeichenfolgen auf der Anmeldeseite-umbenennen hinzugefügt.
  • Die chinesische Sprachdatei aktualisiert.

4.2.7

  • The PHPWhois library updated to their latest version to include a security patch.

4.2.6

  • Added new Login Lockdown whitelist feature which allows immunity for IP address or ranges from being locked by the lockdown feature.
  • Fixed bug – Replaced date_i18n with current_time to prevent cases where some localizations produce foreign characters in date stamp output.
  • Added a new feature to add Honeypot to the WordPress’s user registration form (this can help reduce registration attempts by robots).
  • Added „Export to CSV“ buttons for 404 Event Logs, Account Activity Logs and Failed Login Records.
  • Minor update to 6G rules.
  • Minor spelling and wording fixes and changes.

4.2.5

  • Fixed bug – added code which caters for mysql view definitions when DB prefix is changed.
  • Fixed a typo in the user login security menu.
  • Fixed storage of time stamp in lockdown table to match the local WordPress server time and be consistent with the timestamp stored in the failed logins table.
  • Prevent direct access to wp-security-core.php
  • Updated the POT file.

4.2.4

  • Fix error on block_ip_if_locked(), doesn’t exit with a wp_user. This is needed for other plugins that create the $user (aka ldap auth plugins).
  • Fix login error message for users with pending account approval.
  • WordPress 4.7 compatibility.

4.2.3

  • Fixed bug when math captcha was displayed on Woocommerce registration page.
  • Fixed login page bug for cases where email address and captcha are used to submit login form (thanks to @chesio for fix).
  • Logs directory now contains a .htaccess file with proper deny directives.
  • Small UX improvement: add for attribute to captcha label.
  • Added check for IIS server in get_server_type function.

4.2.2

  • Debug logger class improvements.
  • Added a message in the debug settings area to state that the log files are reset on every plugin update.
  • Always return an array from scan_dir_sort_date() to prevent PHP notices.
  • Verbesserungen für automatisierte DB-Backups, die Speicherplatz belegen – alte Backup-Dateien werden zuerst gelöscht.
  • Vielen Dank an RIPS-Analyzer für die Zusendung des Schwachstellenberichts.

4.2.1

  • Verbesserte Ausgabe von .htaccess mit Checks und RewriteEngine auf Anweisungen.
  • Bei ungültigem Wert wird auf das standardmäßige DB-Sicherungsintervall zurückgegriffen.
  • Die Funktion aiowps_delete_backup_files() erzeugt bei jedem Aufruf eine Debug-Logmeldung (um bei Bedarf bei der Problembehandlung zu helfen).

4.2.0

  • WPML-Plugin-Kompatibilitätsbehebung für die umbenannte Admin-Anmeldeseitenfunktion.
  • Einige potenzielle XSS-Schwachstellen wurden behoben.

4.1.9

  • Kleine Verbesserung der neuen Funktion „Sofortige Sperrung bestimmter Benutzernamen“.

4.1.8

  • Neue Funktion zum sofortigen Blockieren bestimmter Benutzernamen.
  • Aktiviere den Kopierschutz (Rechtsklick) nur für Benutzer ohne Administratorrechte.
  • Es wurde ein Fehler behoben, bei dem der Abmeldelink in der Admin-Leiste nach dem Einreichen von $_POST nicht aktualisiert wurde, um die neue Einstellung für die Anmeldung zum Umbenennen wiederzugeben.
  • Kleiner Fehler in der Funktion return_regularized_url behoben.
  • Verbesserung/Fehlerbehebung: Wenn der aktuell angemeldete Benutzer versucht, auf die umbenannte Anmeldeseite zuzugreifen, leite sie an das Dashboard weiter.
  • Spanische Sprachdateien wurden entfernt, sodass sie automatisch aus WordPress.org gezogen werden können.
  • Lasse die unnötige WHERE-Klausel in einigen Backend-Listen fallen.
  • Verbesserung: Plane keinen Cronjob, wenn er bereits geplant ist.

4.1.7

  • Added sanitisation for log file data in textarea.
  • Disabled autocomplete for Captcha field.

4.1.6

  • Added cleanup code for captcha string info transients.
  • Minor change to the username label in the renamed login page to keep it inline with the standard WordPress login page.
  • Fixed a potential vulnerability when viewing AIOWPS log files in the Dashboard menu. Thanks to Manuel LLOP for pointing this out.

4.1.5

  • Fixed bug where username is an email and captcha was being ignored.
  • Reduce memory footprint of database backup.
  • Improvements: Make hard-coded strings localizable.
  • Teilweise Apache 2.3 Kompatibilität.
  • Improved: Hide WP version number by replacing it with a hash. This way, WordPress version number is not exposed, but browser caching is not obscured by missing version numbers.

4.1.4

  • Improved and tweaked the login captcha feature to avoid some issues people had with the last modification.
  • Deleted reference to ini_get(’safe_mode‘) to avoid fatal errors for newer versions of PHP where that setting has been totally removed.

4.1.3

  • Added new checkbox for XMLRPC to disable only pingback methods but leave other XMLRPC functionality accessible. This will be useful for people who use Jetpack or WordPress iOS or other apps.
  • Die französische Sprachdatei wurde aktualisiert.
  • Fix: decbin doesn’t add leading zero. Comparing empty strings return bad results.
  • Fix: bugfix in the login captcha. Thanks to Sipke Mellema for pointing it out.

4.1.2

  • Fixed bug introduced by last file change scanner code changes.
  • Fixed bug in SPAM comment blocking functionality.
  • Fixed fatal error case when Divi theme and front end lockout is enabled.

4.1.1

  • Fixed Fatal error conflict between Rename Login feature and Yoast SEO and some themes when attempting to access wp-admin page directly.
  • Added „Pending Approval“ message when manual registration approval feature is enabled and a user registers.
  • Fix (minor): No need to use strcmp to compare integer values.
  • Updated and simplified wp-security-stop-users-enumeration.php for bug (thanks to @davidegiunchidiennea)
  • Minor code cleanup (Thanks to @chesio for the following changes).
  • File scanner codebase cleanup.
  • Fix: properly report invalid email addresses in file scanner configuration.
  • Code clean-up in AIOWPSecurity_Scan::do_file_change_scan() method.
  • Tweak: Compare file scan data faster.

4.1.0

  • Fixed bug in Maintenance menu page when trying to attach a media file to the message text box.
  • Added a new filter (called „aiowps_ip_blocked_error_msg“) which allows the modification of the error message displayed on the login page when an IP address has been blocked by the login lockdown feature.
  • Updated French language translation. Thanks to Claude Ribaux for providing the translation files.
  • Thanks to @chesio for making the following two changes.
  • Replaced deprecated call to get_currentuserinfo() function.
  • Minor code fixes in the backup class file.
  • Fix: display correct (error) message when write_to_htaccess() fails.
  • Tweak: database backup filename is more human-readable.
    Before: 24x7eg8l6i-database-backup-1463042767.zip
    After: database-backup-20160512-104607-24x7eg8l6i.zip

4.0.9

  • Made file change scanner code more robust for cases when open_basedir restriction is in effect. (Thanks to Manuel Jeanne for pointing this out).
  • Added code which will remove WordPress version info during CSS and JS script loading if you have the „Remove WP Generator Meta Info“ option checked. (Thanks to aldemarcalazans for pointing this out).
  • Fixed some potential SQL injection vulnerabilities. (Thanks to Julio Potier for pointing these out).
  • Changed the feature category of blacklist manger from „Intermediate“ to „Advanced“.
  • Tweak: Remove „@“ from list of characters blocked by advanced character string filter. (Because it is often used in retina-ready images).
  • Fix: Use home URL instead of site URL in lock notification email subject. Thanks to @chesio for fixing this.

4.0.8

  • Added ability to identify IP addresses during user registration and option to block selected IPs.
  • Added login form captcha functionality for sub-sites in a multi-site installation. (see the Brute Force menu)
  • Fixed multi-site bug related to manual user-chosen DB prefix change.
  • Added extra XSS protection inside admin menu pages for the „tab“ query parameter.
  • Added a note to the features that has the potential to lock you out if it doesn’t work correctly on your site.
  • Updated Brazil-Portuguese language file.
  • Fixed issue with firewall custom rules being corrupted by magic quotes. Thanks to @chesio for fixing this.

4.0.7

  • Added a new action hook „aiopws_before_set_404“ which triggers just before the AIOWPS sets a 404. (handy for cases when rename login page is used which affects some themes when accessing „wp-admin“ directly)
  • Fixed some potential SQL injection vulnerabilities.
  • Thanks to @chesio for submitting the following changes and applying the fixes.
  • Sub-directory install fixes.
  • Improve behavior of WP File Access tab.
  • Fix invalid nesting of HTML elements.
  • Do not block HTTP requests that contain „tag=“ in query string.
  • Option to enable the 6G firewall.

4.0.6

  • Removed the viewing of contents of wp-config.php and .htaccess files in order to protect sensitive info.
  • Fixed more potential XSS vulnerabilities in some other settings pages. (Once again many thanks to Erin Germ for pointing these out)

4.0.5

  • Fixed some potential XSS vulnerability in the blacklist, file system and file change detection settings pages. (Many thanks to Erin Germ for pointing these out)

4.0.4

  • Added new feature: Auto Block Spammer IPs. This feature will automatically and permanently block IP addresses which are linked to comment SPAM. (see SPAM Prevention -> Comment SPAM IP Monitoring tab)
  • Added compatibility fix for the qTranslate-X plugin in the rename login page feature.
  • Added ability to send to more than one email address for file change detection feature notification.
  • Fixed bug in whois library when searching ARIN registry.
  • Fixed the handling of display of longer IPV6 strings in dashboard summary table.
  • Added hook for WooCommerce login form to display unlock button.
  • Added Dutch language translation. Thanks to Jeroen van der Linde for providing the translation files.
  • Typo fix in the „stop users enumeration“ feature.

4.0.3

  • Added urlencode to query strings in URLs to prevent unexpected behaviour. Thanks to @chesio for spotting the issue.
  • Added new feature to stop users enumeration. Thanks to Davide Giunchi @davidegiunchidiennea for adding this.
  • Added a more robust code for check_user_exists function. Thanks to Christian Carey.
  • Added cron cleanup of the global meta table.
  • Added a title in each of the admin interface menu.

4.0.2

  • Added ability to enable/disable debug from the settings menu.
  • Fixed bug related to using IP ranges in the whitelist settings.
  • Added IPv6 support for the whitelist feature.
  • Added check in file permissions feature for cases where wp-config.php may be located outside of root.
  • Added wp cron DB cleanup events for various tables which may grow large over time.
  • Changed firewall rule for proxy comment prevention to reflect suggestion made by Thomas O. in forum (https://wordpress.org/support/topic/high-server-cpu-with-proxy-login)
  • Fixed CSS styling issue in admin pages for WordPrss 4.4

4.0.1

  • Renamed the language files to match the new textdomain slug to fix the language translation bug.
  • Fixed bug related to the rename login feature and force logout or logout expiry events.
  • Applied fix for log being generated by events table DB insert.
  • Corrected a function call to static version of display error msg.

4.0.0

  • Updated text domain to match expected value for translate.wordpress.org translation system.
  • Fixed bug related to multi-site user_roles not being updated for child sites.
  • Fixed minor bug in rename login feature.
  • Die italienische Sprachdatei wurde aktualisiert.

3.9.9

  • Fixed an issue with the rename login page feature for WordPress 4.3
  • Added esc_attr() sanitization to some of the relevant parameters
  • Added the necessary changes to allow activation via wp-cli

3.9.8

  • Added guard against possible XSS in the unlock request feature.

3.9.7

  • Added new feature which allows custom .htaccess rules. (See „Custom Rules“ tab in Firewall menu). You can now use this to add custom rules to block access to various resources on your site.
  • Added a new feature to block access to the wp-content/debug.log file (WordPress creates this file if you enabled debug loggin option in the config file).
  • Removed the „v“ from version number of the plugin.
  • Abgeschlossenes Testen mit WordPress 4.3.

3.9.6

  • Added Rename Login page feature from the „Brute Force“ menu to multisite sub-sites.
  • Removed invalid „length“ attribute from input element in captcha code.
  • Fixed reset password feature whereby the URL which is sent out in the email for cases when rename login feature is enabled was not decoded properly.
  • Corrected the check for boolean false if returned from wpdb query result.
  • Added media button for wp editor in maintenance settings page.

3.9.5

  • Fixed minor bug – IP addresses blocked due to ‚404‘ were not being listed in the display table.
  • Die russische Sprachübersetzungsdatei wurde aktualisiert.
  • The automatic database table prefix generation value will use a-z characters only.
  • Added esc_url sanitization to the add_query_arg/remove_query_arg function instances to prevent possible XSS.

3.9.4

  • The sort order and orderby parameters now use a whitelisting approach for sanitization.

3.9.3

  • Fixed the sort order not working in the 404 error logging and account activity page.

3.9.2

  • Added a check for registration captcha feature to prevent errors when using another captcha plugin.
  • Ein paar SQL-Anweisungen verbessert.

3.9.1

  • Added new „Force Logout“ feature which will instantly force a certain user to be logged out of their session. (See the „Logged In Users“ tab in User Login menu)
  • Added more security protection for aiowps log files by creating .htaccess file and rules. AIOWPS log files can now only be viewed via dashboard menu, in new tab called „AIOWPS Logs“. (NOTE:This security currently applies only for apache or similar servers)
  • Added backticks to SQL statement for DB prefix change to help prevent errors.
  • Added protection against possible SQL injection attacks.

3.9.0

  • Added some robustness to the file-scan code.
  • Added extra security to all relevant list table instances to prevent unlikely malicious deletion commands.
  • Fixed the user agent part of the blacklist settings code to allow user-agents to be cleared upon saving.

3.8.9

  • Fixed bug in the new feature which allows permanent blocking of IP addresses that create 404 events.
  • Fixed minor bug for all instances where wpdb „prepare“ was being used with order/orderby parameters.
  • Fixed a possible open redirect vulnerability. Thanks to Sucuri for pointing it out.

3.8.8

  • Added extra robustness and security for wp list table db commands by using wpdb „prepare“ command.
  • Fixed minor bug with undeclared variable in rename login feature page.

3.8.7

  • Added an improvement for login lockdown feature – locked IP addresses will no longer be allowed to register.
  • Added a „view“ link for each account in the pending registration approval table list.
  • Fixed 404 logging/lockout bug.
  • Added ability to permanently block IP addresses from the 404 event list for both bulk and single cases.
  • Added ability to do bulk temp blocking for IP addresses in 404 list.
  • Fixed a minor bug with validate_ip_list function.

3.8.6

  • DB cleanup cron event bug fixed.
  • Added Swedish language translation. The translation was submitted by Tor-Björn Fjellner.
  • Die russische Sprachübersetzungsdatei wurde aktualisiert. Aktualisierung eingereicht von Tor-Björn Fjellner.
  • The events table will automatically be cleaned up so it only keeps the last 5000 entries. You can override it using a filter (if you wanted to).

3.8.5

  • Added functionality to prevent the aiowps_events table from getting too large.
  • Added file change scan summary inside the alert email.
  • Fixed the unlock feature so that it works correctly when the Rename Login Page feature is active.
  • Added a check in the list logged in users file to prevent error when get_transient returns false.

3.8.4

  • POT-Sprachdatei aktualisiert.
  • Tweaked the function which retrieves the IP address to handle cases where traffic is coming from cloudflare
  • The MySQL database will not be forced anymore at the time of creating the table. It also reads the characters set value from the system first.
  • Applied fixes to prevent remotely exploitable vulnerabilities.

3.8.3

  • Modified „Pingback Protection“ .htaccess rules to prevent xmlrpc login attacks and to be compatible with more servers.
  • Made improvements to ensure that the rename login and white list features can be used together.
  • Added a check to force user to enter alphanumeric string for renamed login slug.
  • Improved the turn_off_all_firewall_rules() and turn_off_all_security_features() functions so that they also handle the updating of the htaccess file.
  • Added an alternative way to import settings via a text box (Thanks to Dave McHale). This is for people who might have issues using the config settings file uploader.
  • Added fix to properly update options tables when changing DB prefix in multisite system.
  • Greatly improved the Renamed Login Page feature by removing various potential vulnerabilities.
  • Added an if statement check to fix bug with rename login page feature – special case where user had non permalink structure was not working correctly in some rare scenarios.
  • Die italienische Sprachdatei wurde aktualisiert.
  • Fixed bug regarding wp_mail malformed header when „From“ string was empty due to „site title“ not being set.
  • Fixed bug in IP list validation function for blacklist feature.
  • Removed strict filtering of IP addresses so as to allow internal IP address ranges.
  • Added stripping of orderby and order query parameters in the plugin.
  • Added search capability by IP address, URL or referer for the 404 events list table.

3.8.2

  • Fixed a CSS issue with the honeypot feature.
  • Fixed a call to the login action handler static function.

3.8.1

  • Minor bug fix for the honeypot feature – loading of css style sheet was not occurring when main login page rendered.

3.8.0

  • Improved deactivation and re-activation tasks – AIOWPS will now gracefully clean up the .htaccess rules when the plugin is deactivated.
  • Tweaked code so that all login pages including custom ones will correctly load the CSS style sheet file needed for honeypot feature.
  • Die portugiesische Sprachübersetzung wurde aktualisiert.
  • Fixed the copy protection feature so it doesn’t interfere with iframes and shortcodes.
  • The plugin will now work fine even if your wp-config.php file is outside the wordpress root folder.

3.7.9.2

  • copy protection feature JS code improvement

3.7.9.1

  • Added captcha functionality for custom login form which is produced by the WP function: wp_login_form()
  • Fixed a minor bug with the copy protection feature’s JavaScript code.
  • Tweaked file change scan algorithm to help prevent getMTime fatal runtime errors.
  • Added a link to the github repository in the readme.txt file for developers.

3.7.9

  • Fixed a small bug related to the cookie test in the Cookie Based Brute Force feature.

3.7.8

  • Added new feature called Login Honeypot which will help reduce brute force login attempts by robots. (This can be found in the Brute Force menu)
  • Added new feature to prevent other sites from displaying your content via a frame or iframe. (This can be found in the Miscellaneous menu)
  • Added captcha feature for BuddyPress registration form.
  • Added a new filter for the site lockout message so it can be customized.
  • Added a new filter for template include of the site lockout feature.
  • Temporarily deactivated the „DB Scan“ feature.

3.7.7

  • Improved DB prefix change code to make it more robust.
  • Fixed a minor bug for the Rename Login page feature.
  • Added check when processing rename login page to see if maintenance (lockout) mode enabled. Plugin will now display lockout message instead of 404 page if site lockout enabled.
  • Made the Cookie Based Brute Force Prevention feature more secure by introducing a 10 digit random suffix to the test cookie name.

3.7.6

  • Added ability to insert captcha in WordPress Multi Site registration form.
  • Added a condition around the management permission constant. This will allow users to define a custom capability for this plugin’s admin side via the wp-config file. This was submitted by Samuel Aguilera.
  • Fixed a bug with the hidden login page feature.
  • Fixed a small settings bug with the „block fake google bot“ feature.

3.7.5

  • Added a new DB scan feature. Go to the „Scanner“ menu to use this new feature.
  • Added new settings import/export feature.
  • Modified user accounts feature to alert administrator if one or both „admin“ or „Admin“ usernames are being used.
  • Added Persian language translation. The translation was submitted by Amir Mousavi Pour (me@ameer.ir).
  • Small change to get_mysql_tables function to prevent fatal error when mysqli query is unsuccessful.
  • Added Italian language translation. The translation was submitted by Marco Guglielmetti.

3.7.4

  • Added a new feature to add copy protection for your front-end. You can find this feature under the „Miscellaneous“ menu.
  • Fixed comment captcha bug for multi-site. Now this feature can be activated/deactivated for subsites of a multisite installation.
  • Added Hungarian language translation. The translation was submitted by Daniel Kocsis.
  • Moved the custom login page feature’s handling code to wp-loaded hook so other plugins that modify the login page can do their task before our one is triggered. This change was suggested by Mark Hudnall.
  • Added German language translation. The translation was submitted by Manuel Fritsch.
  • Die brasilianische Sprachübersetzungsdatei wurde aktualisiert.

3.7.3

  • Added Brazilian language translation. The translation was submitted by Sergio Siqueira.
  • Added two new action hooks for plugin activation and deactivation time.
  • Improved the get_user_ip_address() function so it handles cases when multiple addresses are returned due to proxy.
  • Fixed the mis-alignment of login page which was broken by WP3.9 when rename login feature is used.
  • WordPress 3.9 -kompatibilität

3.7.2

  • Added a PHP Info section in the system info interface to show some important PHP details of the server.
  • Added a filter to allow the user to have a custom translation in a place (which will be loaded instead of the default one from the plugin). This change was submitted by Samuel Aguilera.
  • Replaced myslqi fetch_all method with fetch_assoc to cover cases where some servers do not have the correct mysql drivers.
  • Added a new filter to allow manipulation of the htaccess rules from your custom code. The name of the filter is ‚aiowps_htaccess_rules_before_writing‘.
  • Added a „Delete All 404 Event Logs“ button to purge all 404 logs from DB
  • Added code to automatically send an email to the registrant when an account has been manually „Approved“ from the User Registration menu.

3.7.1

  • Fixed a minor bug: dashboard link was pointing to the wrong tab for the „Logged In Users“ tab.
  • Fix a bug with the login page captcha. The captcha wansn’t shown if the rename login page feature was enabled at the same time.

3.7

  • Added new feature – 404 detection. This allows you to log 404 events and block selected IPs. This feature can be found in the Firewall menu.
  • Added new dashboard info box to display number of blocked IP addresses in the lockout table.
  • Fixed bug where user could not access login page when maintenance mode and rename login page features were both active.
  • Tweaked the hotlinking .htaccess directives to cover both http and https.
  • Fixed code to prevent mysql errors due to some variables not having default value in failed login and lockdown tables
  • Replaced deprecated PHP function mysql_query with mysqli.
  • Added language file for Spanish language. The Spanish translation was done by Samuel Montoya.
  • Added code to hide the „DB Prefix“ menu for the non-main sites in multi-site installation

3.6

  • Added a new feature to prevent image hot-linking. (See the „Prevent Hotlinks“ tab in the firewall menu)
  • Added a check in the Rename Login Page feature to prevent people from setting the slug to „wp-admin“
  • Fixed a small bug with Login Lockdown feature.

3.5.1

  • Fixed a bug where the cookie-based brute force directives were not being deleted from the .htaccess file when the Rename Login Page feature was being activated.

3.5

  • Added new feature which will Block Fake Googlebots from crawling your site. Check the Firewall menu for this new feature.
  • Added code to prevent users from having both the Rename Login Page and Cookie-Based Brute Force features active at the same time.
  • Added some useful info boxes in the dashboard: 1) to inform the user if the cookie based brute force or rename login page features are active, 2) last 5 logins to your site.
  • Fixed minor bug with .htaccess backup feature.
  • Updated the from email address value used for sending backups and file change notification. Thanks to @TheAssurer for the tip.
  • Updated the warning message for the disable index view feature.

3.4

  • Consolidated „Brute Force“ features by moving all such features to the „Brute Force“ menu.
  • Improved the file change detection scan feature: Introduced a button allowing admin to view the file change results from the last scan and fixed small bug whereby the change detected flag was not being cleared for applicable cases.
  • Fixed a small bug with „rename login page“ (hide admin login) feature.
  • Made wp-config.php and .htaccess file backups more secure. Thanks to @TheAssurer for the tip.
  • Made the login code more robust by catering for cases where the „wp_login“ action was not passing 2 parameters.

3.3

  • Added a brand new brute force prevention feature – Rename Login Page. This feature can be found in the new menu item called „Brute Force“.
  • Modified the new unlock request feature so that the locked out user will only have to enter email address when they submit an unlock request.
  • Replaced the deprecated PHP function „mysql_list_tables“ with alternative code.
  • Added warning message regarding WordPress iOS app when pingback protection feature in the firewall settings is active.
  • Added Malware scan tab and information.
  • Some minor html form and CSS corrections.

3.2

  • Added new feature which allows users to generate an automated unlock request link via email when they get locked out because of the login lockdown feature.
  • Added a check to ensure that user cannot enter 0 minutes in the Force Logout feature.
  • Fixed translations so that various previously omitted strings can now be translated.
  • Added a new filter before locking down a user’s IP address – aiowps_before_lockdown.
  • Generated a new translation (POT) file.

3.1

  • Added a new feature that will allow you to add a captcha to the lost password form (useful if you are allowing user registration on your site).
  • Added ability to specify a system log file in the „Host System Logs“ tab of the „File System Security“ menu
  • Fixed a tab link bug. One link was going to the wrong menu tab.
  • Die POT-Datei des Plugins wurde aktualisiert.

3.0

  • Added a new feature which allows you to add captcha to the WordPress user registration page.
  • Added some more helpful comments and link to video tutorial in the brute force and white list features settings pages.

2.9

  • Added new feature which automatically sets the status of newly registered wordpress user accounts to „pending“ and allows manual approval by an administrator.
  • Improved robustness of file change detection iteration code.
  • WordPress 3.7 -kompatibilität

2.8.1

  • Improved the login captcha implementation
  • Changed the management permission to manage_options

2.8

  • Added a feature to insert a simple math captcha to the WordPress comment form (to reduce comment spam). Check the spam prevention menu for this new feature.
  • Fixed a minor bug with bulk unlock/delete in user login menu
  • Fixed a minor bug with math captcha logic.

2.7

  • Added a simple math captcha functionality for the WP login page. This is another easy yet effective way to combat Brute Force Login Attacks. You can enable this new feature from the user login security menu.

2.6

  • Added a new Login Whitelist feature. This feature enables you to specify one or more IP addresses in a special whitelist which will have access to your WP login page.
    All other IP addresses trying to access your WP login page which are not in the whitelist will be automatically blocked.
  • The IP address will also be included in the email that gets sent to the admin for the ip address lockout notification.
  • Language file loading fix for Chinese language.
  • Tweaked the code which creates a .htaccess file in the backup directory to ensure it gets run even if the directory already existed.
  • Made DB backups more secure.
  • Added more useful debug logs for .htaccess file manipulation failure scenarios.

2.5

  • Added a new feature which will list the currently logged in users who have been active within the last 15 minutes.
  • Added a new feature in settings menu which will disable all firewall rules and clear all applicable directives in the .htaccess file.
  • Improved the way the wp-config.php file is handled when it contains an ending PHP tag „?>“ (older sites that were using PHP4 earlier).

2.4

  • Added new feature/checkbox which will instantly lockout IP address ranges which attempt to login with an invalid username.
  • Fixed a bug in the Comment SPAM IP Monitoring page where trying to block one or more IPs was failing.
  • Removed the word „config“ from the list of bad query strings check (to add compatibility with a few more plugins)
  • Added a notice in the dashboard menu to show you if there are any recent file changes that the plugin detected.
  • Fixed bug with php File Editing feature. Code now also handles older style wp-config.php files which have the php end tag „?>“
  • Fixed bug with „Disable All Security Features“ button functionality. When clicked, this will now also make the appropriate changes to the .htacces and wp-config.php files if necessary.
  • Changed the storage of backup files from the plugin’s directory to the uploads directory. Also added a .htaccess file for security.
  • Fixed the way user-agent strings were written to the .htacess file from the Blacklist feature. The code now will correctly identify and represent spaces and escaped chars.
  • Fixed a bug related to sending backup to correct email address.

2.3

  • Added new menu called Scanner with a new feature called File Change Detection. This feature will alert you if any files have changed, added or removed from your system.
  • Fixed „Deny Bad Query Strings“ rules to not break the ability to drag components in the WordPress „Appearance->Menus“ page
  • Fixed an activation time warning (on sites with WP_DEBUG option enabled)
  • Re-implemented the wp-config.php file content backup feature. It now directly downloads the contents of the file to your computer.
  • Multi-site enhancements: Suppressed access to configuration settings for features which are not allowed to be configured from subsites of multi-site installations.
  • Fixed a bug with login lockdown feature.

2.2

  • Added a new feature which will block some spambots from submitting comments.
  • Moved Comment SPAM IP monitoring interface to the new „SPAM Prevention“ menu.
  • Fixed a bug with login lockdown feature for both multi and single site.
  • Improved firewall feature for multi-site by making the „Firewall“ menu available only for the main site and not the sub-sites.
  • Added random prefix to backup file names.
  • Fixed a bug for WP multi-site install where DB tables do not get created when new blog are created in the network.

2.1.1

  • Fixed a version tagging issue.

2.1

  • Fixed an issue with install time error on some sites for WordPress 3.6
  • Fixed some WP Debug related errors for WordPress 3.6
  • Replaced the deprecated $wpdb->escape() function calls with esc_sql() calls

2.0

  • Fixed a bug for general DB backup functionality.
  • Fixed multi-site DB backup – the plugin will now backup only the tables relevant for the sub-site in question.
  • Added blank index.html files in various folders inside the plugin.
  • Disabled the wp-config.php file backup feature until we find a more secure method of doing the backup.

1.9

  • Added new WordPress PingBack Vulnerability Protection feature. This allows the user to prohibit access to the xmlrpc.php file in order to protect against certain vulnerabilities in the pingback functionality.
  • Added a configuration item in the brute force login prevention feature to allow ajax functionality to work properly when this feature is enabled.
  • Added a POT file for language translations.
  • Made the DB Prefix feature more robust by adding a check to ensure that plugin can write to the wp-config.php file. This will prevent user from losing access to their site in cases where the system changed the prefix but not the entry in the wp-config.php file.
  • Tightened the data validation for the cookie based brute force login feature to ensure that the user must enter a secret word which consists of alphanumeric characters.
  • Added edit links to the user account list in the „User Acounts“ menu.

1.8

  • Moved the front end site lockout feature to a new menu called „Maintenance“.
  • Added a feature in the front-end lockout feature to allow people to specify their own message which will be displayed on the front-end to visitors who try to access the site when it is in lock out state.
  • Fixed a bug in the front-end lockout feature by adding some checks which ensure that the admin will not get locked if the feature is still active and their login session expires or they log out.
  • Added a widget in the dashboard menu to show the status of the „maintenance mode“ feature.

1.7

  • Added a new feature which is a password strength tool which calculates how easy it is for your chosen password to be cracked using a desktop PC and the appropriate SW. This tool should help you create strong passwords.
  • Added a front-end general visitor lockout feature. This feature allows you to temporarily lock down the front end of your site while you do security investigation, site upgrades, tweaks etc.

1.6

  • Added a new option in the cookie-based Brute Force Login Attack prevention feature to allow users to use this feature together with the WordPress’s post/page password protection feature.
  • Fixed a bug in the 5G firewall rules to so that the printed rules include the correct number of ‚\‘ characters.
  • Fixed a minor bug in the „restore from backed up htaccess file“ feature.
  • Enhanced the „Save current wp-config.php file“ feature so it will continue to work with all of the firewall rules active on the site.
  • Added extra checks to account for some error scenarios caused on some servers when recursive file search is done.

1.5

  • Added new feature – Cookie-based Brute Force Login Attack Prevention. Check under the „Firewall“ menu for this new feature.
    This feature will stop hackers in their tracks when they try to access your wp-admin or login pages. This feature will secure your WordPress backend by enforcing the requirement that anybody trying to access these pages will require a special cookie.

  • Fixed bug related to setting of default configuration for first-time plugin activation.

1.4

  • Tweaked the „Deny Bad Query Strings“ firewall rules so that plugin deletion and update operations from the WordPress plugins menu are not affected.
  • Fixed a minor bug related to scheduled database backups.
  • Added some extra default settings to be applied to the plugin’s configuration pages upon activation for the first time.
  • Plugin will now display a recommendation message if user sets scheduled backup frequency to less than 24 hours.

1.3

  • Added a new feature to remove the WordPress Generator Meta information from the HTML source of your site.
  • Tweaked the „Advanced Character String Filter“ to fix issue which was affecting plugins such as „Admin Management Xtended“ and also pages with keywords such as „password“ in the URL.
  • Updated one rule in the „Advanced Character String Filter“ feature to make it compatible with W3 Total Cache Plugin’s minify feature.
  • Added a „Delete All Failed Login Records“ option in the „Failed Login Records“ tab. This will delete all entries in the failed logins table and will make it less tedious for users who get a lot of brute force attacks on their site.

1.2

  • Moved the rules which disable index views from the „basic firewall“ rules to the „additional rules“ section. This will prevent any site breakage for
    those who want to enable the basic firewall but do not have „AllowOverride“ option enabled in their httpd.conf

1.1

  • Added the following new feature:
  • Prevent people from accessing the readme.html, license.txt and wp-config-sample.php files.

1.0

  • First commit to the WP repository.