Linux 软件免费装
Banner图

WPBruiser Security - No CAPTCHA Anti-Spam & Login Protection

开发者 mihche
wpzoom
更新时间 2026年11月14日 20:11
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

captcha security anti-spam brute force limit login attempts

下载

3.6.3 2.0 2.1.0 2.2.2 3..1.27 3.0.10 3.0.11 3.0.12 3.0.14 3.0.5 3.0.8 3.0.9 3.1.1 3.1.10 3.1.11 3.1.12 3.1.14 3.1.18 3.1.19 3.1.20 3.1.23 3.1.25 3.1.26 3.1.28 3.1.29 3.1.3 3.1.31 3.1.33 3.1.34 3.1.35 3.1.36 3.1.37 3.1.38 3.1.40 3.1.42 3.1.5 3.1.7 3.1.8 3.6.4 3.3.1 3.7.0 3.3.0 3.0.15 3.1.43 3.2.1 3.4.0 3.5.0 3.6.0 3.6.1 3.6.2

详情介绍:

WPBruiser stops automated form submissions before WordPress ever processes them. Every protected form gets a hidden token, which the visitor's browser requests in the background. A real person never sees it or has to do anything. A bot that posts straight to your login, registration or comment endpoint arrives without a valid token and is turned away. Because bad submissions are rejected at the door, they never land in your moderation queue and never create junk user accounts. You also don't have to ask visitors to solve a puzzle, which is often the step where real people give up on a form. Everything runs on your own server. WPBruiser does not call remote APIs, does not load outside scripts or fonts and does not send your visitors' data anywhere. Notice: As of version 3.2.0, it is maintained by WPZOOM. Forms you can protect Turn protection on or off for each form on the WordPress and Integrations screens: Free integrations Each integration is a card on the Integrations screen, which shows whether its plugin is active on your site and has one switch to turn protection on. On a new install, protection is switched on for every supported plugin that is already active. Login With Ajax and wpDiscuz need no switch of their own: they are covered by the WordPress login and comment protection. Using Contact Form 7, WPForms, WooCommerce, Easy Digital Downloads, Elementor Pro, Gravity Forms or another popular form plugin? WPBruiser Pro protects them too. See "WPBruiser Pro" below. Brute-force and hardening tools IP address management Reports Everyday details WPBruiser Pro WPBruiser Pro is an add-on from WPZOOM that brings the same invisible check to the form, shop and newsletter plugins most sites run on. It adds its integrations to the Integrations screen you already know, so there is nothing new to learn, and it keeps every check on your own server. Form builders Shop and newsletters Security Also included Compare free and Pro, and see the plans External services All spam and bot detection happens on your server. WPBruiser collects no telemetry, runs no license or update checks of its own and loads no third-party fonts or scripts, and the IP reputation and country data it uses ship inside the plugin. Nothing about your visitors is ever sent anywhere. The one external service is the WordPress.org plugin directory, for the plugin check: Support Found a bug or have a question? Start a topic on the WordPress.org support forum. It helps us a lot if you include your WordPress and PHP versions, the form or plugin involved, and the steps that reproduce the problem.

安装:

From your dashboard
  1. In the WordPress admin, open Plugins > Add Plugin.
  2. Search for "WPBruiser", then click Install Now and Activate.
Manually
  1. Download the plugin ZIP from WordPress.org.
  2. Either upload it under Plugins > Add Plugin > Upload Plugin, or extract it and copy the goodbye-captcha folder into wp-content/plugins/ on your server.
  3. Activate WPBruiser on the Plugins screen.
First steps after activating
  1. Open the new WPBruiser item in the admin menu.
  2. On the WordPress screen, check that the login, registration, lost password and comment forms are protected (they are on a new install).
  3. On the Integrations screen, switch on protection for any supported plugin you use. Integrations for plugins that are already active are switched on for you on a new install.
  4. Optionally, turn on Test Mode, submit your forms yourself and check the notification emails. Turn Test Mode off when you're done.
  5. If your site is behind a reverse proxy or CDN that isn't detected automatically, add its header under trusted proxy headers so the correct visitor IP is logged.
On a Multisite network, activate the plugin network-wide and manage it from the Network Admin.

屏幕截图:

  • Choosing which core WordPress forms to protect, with optional comment field limits
  • Reports: blocked attempts per day and per form, and the latest attempts
  • Inspecting the content of a blocked comment
  • Blocked attempts by country and by integration, with one-click IP blocking
  • The Dashboard widget with blocked attempts for the last day, week and month
  • Brute-force protection and the allow and block lists for IP addresses
  • General settings, including Test Mode and how long logs are kept
  • Email notifications for brute-force attacks and administrator logins
  • WPBruiser Pro: Contact Form 7, WPForms, WooCommerce and more on the same Integrations screen
  • WPBruiser Pro: country blocking and submission rate limits on the Security screen

常见问题:

Will my visitors notice anything?

No. There is nothing to click, type or solve. The check runs quietly in the browser while the form is on screen.

Does it need JavaScript?

Yes. The token that proves a submission came from a real browser is generated by a small script. Visitors who have JavaScript turned off will not be able to submit the forms you protect.

How can I check that it is working?

Turn on Test Mode in the plugin settings. While it is on, nothing is blocked. Instead, the notification address receives an email for each checked submission, so you can try your own forms and see the result. Turn Test Mode off afterwards. From then on, the Reports screen lists every attempt that was blocked.

I use a page caching plugin. Is that a problem?

No. The script requests a fresh token on every page view. If a cached copy of a page carries an expired security key, the script gets a new one first, so you don't have to exclude any pages from your cache.

My site is behind Cloudflare or another proxy. Will the right IP be blocked?

The common proxies and CDNs are recognised automatically. For anything else, add the proxy's HTTP header on the proxy headers settings screen. Otherwise every visitor may appear to have the proxy's IP address.

I locked myself out. What now?

If you mistyped your password too many times, wait for the lockout to end (20 minutes by default) or log in from another connection and press Release on the Security screen. If you moved the login page and lost its address, add define('WPBRUISER_DISABLE_LOGIN_URL', true); to wp-config.php to use wp-login.php again; the address was also emailed to the site admin when you set it. To avoid both, add your own IP address to the allow list. Allowed addresses skip all checks, including the block list. If you can't reach the dashboard, rename the wp-content/plugins/goodbye-captcha folder over FTP or with your host's file manager to deactivate the plugin. Then sign in, rename it back and add your address to the allow list.

What does WPBruiser Pro add?

Protection for Contact Form 7, WPForms, Elementor Pro forms, Gravity Forms, Fluent Forms, Forminator, Ninja Forms, Formidable Forms, WooCommerce, Easy Digital Downloads and MailPoet, plus country blocking, submission rate limits and priority support. See "WPBruiser Pro" in the description, or the WPBruiser Pro page.

Do I still need the free plugin with Pro?

Yes. WPBruiser Pro is an add-on: it adds integrations and security features to this plugin, which keeps doing the checking, the logging and the reports.

Does WPBruiser Pro call any external service?

Only for the license (activation and a daily check) and updates, which come from wpzoom.com. Every check still runs on your server, and the IP-to-country data ships inside the add-on.

Does it send data to any server?

Nothing about your visitors, ever. The only outside request is the weekly plugin check, which sends the names of your installed plugins to the WordPress.org plugin directory, as WordPress itself does for updates. See "External services" in the description. (The optional WPBruiser Pro add-on contacts wpzoom.com for its license and updates, and, only if you set them up, Slack, Telegram or your webhook for the report.)

Does it replace a full security plugin?

No. WPBruiser handles spam bots, brute-force logins and a few hardening options. It doesn't scan files, run a firewall or check your site's integrity, so you can run it alongside a plugin that does.

I'm upgrading from the original WPBruiser. Will I lose my settings?

No. Your settings, allow and block lists and logs are kept, and the upgrade routines run by themselves the first time the new version loads. Two things no longer load: the old paid add-ons, and the integrations for plugins that are closed or no longer maintained (ZM Ajax Login & Register, PlanSo Forms, UltraCommunity, Seamless Donations and Epoch).

Where do I report security bugs found in this plugin?

Please report security bugs found in the source code of the plugin through the Patchstack Vulnerability Disclosure Program. The Patchstack team will assist you with verification, CVE assignment, and notify the developers of this plugin.

更新日志:

3.7.0 3.6.4 3.6.3 3.6.2 3.6.1 3.6.0 3.5.0 3.4.0 3.3.1 3.3.0 3.2.1 3.2.0 Security 3.1.43 3.1.40 Fixes 3.1.39 3.1.38 Fixes 3.1.37 Improvements 3.1.36 Fixes 3.1.35 Improvements 3.1.34 Improvements 3.1.33 Fixes 3.1.32 Improvements 3.1.31 Improvements 3.1.30 3.1.29 Refreshed Incapsula, Amazon and Cloudflare trusted IPs ranges 3.1.28 Fixes 3.1.27 Improvements 3.1.26 Improvements 3.1.22 3.1.21 Improvements 3.1.19 3.1.18 3.1.15 Fixes 3.1.14 Improvements 3.1.12 Fixes 3.1.11 3.1.9 3.1.6 Improvements 3.1.4 Fixes 3.1.3 Improvements 3.1.1 Fixes 3.1 Fixes 3.0.15 Improvements 3.0.14 Fixes 3.0.12 Improvements 3.0.11 Improvements 3.0.10 Additions New Premium Extensions 3.0.9 Fixing repository issues 3.0.7 3.0.6 Fixed corrupted files from WordPress Repository 3.0.5 3.0.4 Fixes 3.0.3 Fixes 3.0.2 3.0.1 Improvements 3.0 Introducing premium extensions 2.2.2 2.2.1 2.2.0 2.1.0 2.0.1 Fixes 2.0 Additions