Beschreibung

fail2ban is one of the simplest and most effective security measures you can implement to prevent brute-force attacks.

WP fail2ban logs all login attempts – including via XML-RPC, whether successful or not, to syslog using LOG_AUTH. For example:

Oct 17 20:59:54 foobar wordpress(www.example.com)[1234]: Authentication failure for admin from 192.168.0.1
Oct 17 21:00:00 foobar wordpress(www.example.com)[2345]: Accepted password for admin from 192.168.0.1

WPf2b comes with three fail2ban filters: wordpress-hard.conf, wordpress-soft.conf, and wordpress-extra.conf. These are designed to allow a split between immediate banning (hard) and the traditional more graceful approach (soft), with extra rules for custom configurations.

Features

NEW – Support for 3rd-party Plugins
Version 4.2 introduces a simple API for authors to integrate their plugins with WPf2b, with 2 experimental add-ons:
- Contact Form 7
- Gravity Forms
CloudFlare and Proxy Servers
WPf2b can be configured to work with CloudFlare and other proxy servers. For an overview see WP_FAIL2BAN_PROXIES.
Comments
WPf2b can log comments (see WP_FAIL2BAN_LOG_COMMENTS) and attempted comments (see WP_FAIL2BAN_LOG_COMMENTS_EXTRA).
Pingbacks
WPf2b logs failed pingbacks, and can log all pingbacks. For an overview see WP_FAIL2BAN_LOG_PINGBACKS.
Spam
WPf2b can log comments marked as spam. See WP_FAIL2BAN_LOG_SPAM.
Block User Enumeration
WPf2b can block user enumeration. See WP_FAIL2BAN_BLOCK_USER_ENUMERATION.
Work-Arounds for Broken syslogd
WPf2b can be configured to work around most syslogd weirdness. For an overview see WP_FAIL2BAN_SYSLOG_SHORT_TAG and WP_FAIL2BAN_HTTP_HOST.
Blocking Users
WPf2b can be configured to short-cut the login process when the username matches a regex. For an overview see WP_FAIL2BAN_BLOCKED_USERS.
mu-plugins Support
WPf2b can easily be configured as a must-use plugin – see Configuration.

Installation

Install via the Plugin Directory, or upload to your plugins directory.
Activate the plugin through the ‚Plugins‘ menu in WordPress.
Edit wp-config.php to suit your needs – see Configuration.

Rezensionen

Works like a charm

nssy

Been using this for a while now. Integration with fail2ban is pretty straight forward.

This plugin is perfect, essential – thank you so much

herculesnetwork

This plugin is perfect, essencial - thank you so much the best thing about this plugin after it works perfectly, is that it does not change the directories nor names of the configuration files, something unpleasant that always happens in plugins, you configure everything for the given file, and a certain directory of the plugin and in a new version unnecessarily the plugin changes the things of place. this plugin I have a long time, and I have a command to copy and paste the w2 fail2ban plugin settings to fail2ban, and things continue as usual. Thanks to the developer. Who does not give 5 stars, does not know how to use it.

Perfect – worked first time

commando

Great plugin, that worked first time. On Amazon Linux / Centos the location of the log file is /var/log/messages

Very useful

sillystring

Great idea if you host your own server and use fail2ban. Thanks!

Just great

FernandoNunes

Works just great with latest version. Keep up the good work.

works great

helix84

Works great and is very flexible. The only thing I'd recommend out of the box is to move the regex for "Authentication attempt for unknown user" from wordpress-hard.conf to wordpress-soft.conf because the former bans the user after first failure (as per the recommended default configuration). ^%(__prefix_line)sAuthentication attempt for unknown user .* from <HOST>$

Lies alle 47 Rezensionen

Mitwirkende & Entwickler

„WP fail2ban“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin mitgewirkt:

invisnet

„WP fail2ban“ wurde in 1 Sprache übersetzt. Danke an die Übersetzerinnen und Übersetzer für ihre Mitwirkung.

Übersetze „WP fail2ban“ 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.2.3

Workaround for some versions of PHP 7.x that would cause define()s to be ignored.
Add config note to settings tabs.
Fix documentation links.

4.2.2

Fix 5.3 compatibility.

4.2.1

Completed support for WP_FAIL2BAN_COMMENT_EXTRA_LOG.
Add support for 3rd-party plugins; see Developers.
- Add-on for Contact Form 7 (experimental).
- Add-on for Gravity Forms (experimental).
Change logging for known-user with incorrect password; previously logged as unknown user and matched by hard filters (due to limitations in older versions of WordPress), now logged as known user and matched by soft.
Bugfix for email-as-username – now logged correctly and matched by soft, not hard, filters.
Bugfix for regression in code to prevent Free/Premium conflict.

4.2.0

Not released.

4.1.0

Add separate logging for REST authentication.
Fix conflict with earlier versions pre-installed in mu-plugins. See Is WPf2b Already Installed?.

4.0.5

Add WP_FAIL2BAN_COMMENT_EXTRA_LOG.
Add WP_FAIL2BAN_PINGBACK_ERROR_LOG (future functionality).
Change WP_FAIL2BAN_LOG_SPAM to use LOG_NOTICE.
Change WP_FAIL2BAN_SPAM_LOG to LOG_AUTH.
Change WP_FAIL2BAN_LOG_COMMENTS_EXTRA events to use LOG_NOTICE by default.
Fix conflict with 3.x in mu-plugins.

4.0.2

Fix PHP 5.3 compatibility.
Bugfix for WP_FAIL2BAN_LOG_COMMENTS_EXTRA.
Bugfix for WP_FAIL2BAN_REMOTE_ADDR summary.

4.0.1

Add extra features via Freemius. This is entirely optional. WPf2b works as before, including new features listed here.
Add settings summary page (Settings -> WP fail2ban).
Add WP_FAIL2BAN_PASSWORD_REQUEST_LOG.
Add WP_FAIL2BAN_SPAM_LOG.
Add WP_FAIL2BAN_LOG_COMMENTS_EXTRA – enable logging for attempted comments on posts which are:
- not found,
- closed for commenting,
- in the trash,
- drafts,
- password protected
Block user enumeration via REST API.

4.0.0

Not released.

3.6.0

The filter files are now generated from PHPDoc in the code. There were too many times when the filters were out of sync with the code (programmer error) – this should resolve that by bringing the patterns closer to the code that emits them.
Added PHPUnit tests. Almost 100% code coverage, with the exception of WP_FAIL2BAN_PROXIES which is quite hard to test properly.
Bugfix for wordpress-soft.conf.
Add WP_FAIL2BAN_XMLRPC_LOG.
Add WP_FAIL2BAN_REMOTE_ADDR.
WP_FAIL2BAN_PROXIES now supports an array of IPs with PHP 7.
Moved all documentation to https://docs.wp-fail2ban.com/.

3.0.2

Prevent double logging in WP 4.5.x for XML-RPC authentication failure

3.0.1

Fix regex in wordpress-hard.conf.

3.0.0

Add WP_FAIL2BAN_SYSLOG_SHORT_TAG.
Add WP_FAIL2BAN_HTTP_HOST.
Log XML-RPC authentication failure.
Add better support for MU deployment.

2.3.2

Bugfix WP_FAIL2BAN_BLOCKED_USERS.

2.3.0

Bugfix in experimental WP_FAIL2BAN_PROXIES code (thanks to KyleCartmell).

2.2.1

Fix stupid mistake with WP_FAIL2BAN_BLOCKED_USERS.

2.2.0

Custom authentication log is now called WP_FAIL2BAN_AUTH_LOG.
Add logging for pingbacks; see WP_FAIL2BAN_LOG_PINGBACKS.
Custom pingback log is called WP_FAIL2BAN_PINGBACK_LOG.

2.1.1

Minor bugfix.

2.1.0

Add support for blocking user enumeration; see WP_FAIL2BAN_BLOCK_USER_ENUMERATION.
Add support for CIDR notation in WP_FAIL2BAN_PROXIES.

2.0.1

Bugfix in experimental WP_FAIL2BAN_PROXIES code.

2.0.0

Add experimental support for X-Forwarded-For header; see WP_FAIL2BAN_PROXIES.
Add experimental support for regex-based login blocking; see WP_FAIL2BAN_BLOCKED_USERS.

1.2.1

Update FAQ.

1.2

Fix harmless warning.

1.1

Minor cosmetic updates.

1.0

Erstveröffentlichung

WordPress.org

Deutsch