WebbPlatsen

joho68

<p>This WordPress plugin provides security functionality and integration with fail2ban.</p>
<p>It does not require fail2ban to function.</p>
<p>Basic security functionality includes:</p>
<ul>
<li>Disabling login with username (require e-mail address)</li>
<li>Allow/Deny login from IP address, hostname (including wildcard support)</li>
<li>Preventing user enumeration (?author=nnn)</li>
<li>Less detailed error messages on login failures</li>
<li>Minimum username length</li>
<li>Blocking specific usernames from being used to register new users</li>
<li>Requiring e-mail address matching for new user registrations</li>
<li>Warning about new user role setting</li>
<li>Blocking of portions or all of WordPress REST API</li>
<li>Disabling of RSS and Atom feeds</li>
<li>Removal of “Generator” information from HTML and feeds</li>
<li>Detection of Cloudflare IP addresses for logging of actual IP addresses</li>
<li>Blocking/Allowing logins from IP addresses, IP ranges, and/or hostnames</li>
<li>Partially or fully disable XMLRPC access</li>
</ul>
<p>The plugin also plays nicely with Fail2ban, which is an advanced way of blocking IP addresses dynamically upon suspicious behavior.</p>
<p>Other notes:</p>
<ul>
<li>This plugin <strong>may</strong> work with earlier versions of WordPress</li>
<li>This plugin has been tested with <strong>WordPress 5.5+ and 6.x</strong> at the time of this writing</li>
<li>This plugin has been tested with <strong>PHP 7.4, and 8.1.x</strong> at the time of this writing</li>
<li>This plugin optionally makes use of <code>mb_</code> PHP functions</li>
<li>This plugin may create entries in your PHP error log (if active)</li>
<li>This plugin contains no Javascript</li>
<li>This plugin contains no tracking code and does not store any information about users</li>
</ul>
<h3>Credits</h3>
<p>The Fail2WP Plugin was written by Joaquim Homrighausen while converting caffeine into code.</p>
<p>Fail2WP is sponsored by <a href="https://webbplatsen.se" rel="nofollow ugc">WebbPlatsen i Sverige AB</a>, Sweden.</p>
<p>Commercial support and customizations for this plugin is available from WebbPlatsen i Sverige AB in Sweden.</p>
<p>If you find this plugin useful, the author is happy to receive a donation, good review, or just a kind word.</p>
<p>If there is something you feel to be missing from this plugin, or if you have found a problem with the code or a feature, please do not hesitate to reach out to support@webbplatsen.se.</p>
<p>This plugin can also be downloaded from <a href="https://code.webbplatsen.net/wordpress/fail2wp/" rel="nofollow ugc">code.webbplatsen.net</a> and <a href="https://github.com/joho1968/fail2wp" rel="nofollow ugc">GitHub</a></p>
<p>More detailed documentation is available at <a href="https://code.webbplatsen.net/documentation/fail2wp/" rel="nofollow ugc">code.webbplatsen.net/documentation/fail2wp/</a></p>
<p>Kudos to <a href="https://github.com/tholu" rel="nofollow ugc">Thomas Lutz</a>.</p>


Fail2WP

Security plugin for WordPress with support for fail2ban. Tested with WordPress 5.5+ and PHP 7.4/8.1.x.

Federico Rota

<p>This plugin writes the log of failed access attempts (brute force attack) and invalids pingbacks requests ( by xmlrpc.php ). Very useful to process data via fail2ban.<br />
You can activate the log for each pingback request feature and stop the user enumeration method (by redirecting to the home) with log.<br />
If activated it remove the wordpress version number and meta generator in the head section of your site.<br />
If activated it disable xmlrpc methods that require authentication, in order to avoid brute force attack by xmlrpc. Use this feature if you don’t need these xmlrpc methods.<br />
If activated can kill multiple requests in a single xmlrpc call returning a 401 code on xmlrpc login error. This feature may be useful to prevent server overloading on brute force attack by xmlrpc.<br />
You can also view your CUSTOM error log in the admin panel.</p>
<h4>You can write error by</h4>
<ol>
<li>SYSLOG</li>
<li>APACHE ERROR_LOG</li>
<li>CUSTOM a custom error log file (the used path need to be writable or APACHE ERROR LOG wil be used)</li>
</ol>
<h4>Log examples</h4>
<ul>
<li>
<p>SYSLOG</p>
<pre><code>Dec 17 14:21:02 webserver wordpress(`SERVER_HTTP_HOST`)[2588]: Authentication failure on [`WORDPRESS_SITE_NAME`] for `USED_LOGIN` from `111.222.333.444`
Dec 17 14:21:02 webserver wordpress(`SERVER_HTTP_HOST`)[2588]: Pingback error `IXR_ERROR_CODE` generated on [`WORDPRESS_SITE_NAME`] from `111.222.333.444`
Dec 17 14:21:02 webserver wordpress(`SERVER_HTTP_HOST`)[2588]: Pingback requested for `PINGBACK_URL` generated on [`WORDPRESS_SITE_NAME`] from `111.222.333.444`
Dec 17 14:21:02 webserver wordpress(`SERVER_HTTP_HOST`)[2588]: User enumeration attempt generated on [`WORDPRESS_SITE_NAME`] from `111.222.333.444`
</code></pre>
</li>
<li>
<p>APACHE</p>
<pre><code>[Thu Dec 17 14:23:33.662339 2015] [:error] [pid 2580:tid 140001350244096] [client 111.222.333.444:52599] wordpress(`SERVER_HTTP_HOST`) Authentication failure on [`WORDPRESS_SITE_NAME`] for `USED_LOGIN` from `111.222.333.444`, referer: SITE_ADDRESS/wp-login.php
[Thu Dec 17 14:23:33.662339 2015] [:error] [pid 2580:tid 140001350244096] [client 111.222.333.444:52599] wordpress(`SERVER_HTTP_HOST`) Pingback error `IXR_ERROR_CODE` generated on [`WORDPRESS_SITE_NAME`] from `111.222.333.444`, referer: SITE_ADDRESS/xmlrpc.php
[Thu Dec 17 14:23:33.662339 2015] [:error] [pid 2580:tid 140001350244096] [client 111.222.333.444:52599] wordpress(`SERVER_HTTP_HOST`) Pingback requested for `PINGBACK_URL` generated on [`WORDPRESS_SITE_NAME`] from `111.222.333.444`, referer: SITE_ADDRESS/xmlrpc.php
[Thu Dec 17 14:23:33.662339 2015] [:error] [pid 2580:tid 140001350244096] [client 111.222.333.444:52599] wordpress(`SERVER_HTTP_HOST`) User enumeration attempt generated on [`WORDPRESS_SITE_NAME`] from `111.222.333.444`
</code></pre>
</li>
<li>
<p>CUSTOM</p>
<pre><code>[Thu Dec 17 14:25:34.000000 2015] wordpress(`SERVER_HTTP_HOST`) Authentication failure on [`WORDPRESS_SITE_NAME`] for `USED_LOGIN` from `111.222.333.444`
[Thu Dec 17 14:25:34.000000 2015] wordpress(`SERVER_HTTP_HOST`) Pingback error `IXR_ERROR_CODE` generated on [`WORDPRESS_SITE_NAME`] from `111.222.333.444`
[Thu Dec 17 14:25:34.000000 2015] wordpress(`SERVER_HTTP_HOST`) Pingback requested for `PINGBACK_URL` generated on [`WORDPRESS_SITE_NAME`] from `111.222.333.444`
[Thu Dec 17 14:25:34.000000 2015] wordpress(`SERVER_HTTP_HOST`) User enumeration attempt generated on [`WORDPRESS_SITE_NAME`] from `111.222.333.444`
</code></pre>
</li>
</ul>
<h4>fail2ban configuration</h4>
<p>See the FAQ section</p>
<h4>Log viewer</h4>
<p>Log viewer is available only in CUSTOM mode. Note: the log path and the file must exist.</p>
<h4>Localization</h4>
<ul>
<li>English (default) – always included</li>
<li>Italian – since 1.1.3 version</li>
</ul>
<h3>Translations</h3>
<ul>
<li>English – default, always included</li>
<li>Italiano – disponibile dalla versione 1.1.3</li>
</ul>
<p><em>Note:</em> Feel free to translate this plugin in your language. This is very important for all users worldwide. So please contribute your language to the plugin to make it even more useful. For translating I recommend the <a href="http://www.poedit.net/" rel="nofollow ugc">“Poedit Editor”</a>.</p>


Authentication and xmlrpc log writer

Log of failed access, pingbacks, user enumeration, disable xmlrpc authenticated methods, kill xmlrpc request on authentication error.

Fail2WP vs Authentication and xmlrpc log writer