ZeroBot Security – Login Protection, Firewall & Bot Blocker
| 开发者 | zerobot |
|---|---|
| 更新时间 | 2026年10月6日 20:03 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
ZeroBot Security protects your site from the first minute, with no account and no setup.
Activate it and two protections start working inside WordPress itself.
Nothing is sent anywhere.
Free, no account needed
- Login Brute-Force Guard — Counts failed logins per IP and locks the IP out after 5 attempts for 15 minutes (both adjustable). Blocks password-guessing bots on wp-login.php.
- XML-RPC Kill Switch — Shuts down xmlrpc.php, the endpoint bots use to try hundreds of passwords in one request and to abuse pingbacks. Skipped automatically when Jetpack is active, because Jetpack needs it.
- Attack counter — The dashboard shows how many failed logins, lockouts and XML-RPC requests were stopped over the last 7 days.
- Spoof-proof IP detection — Proxy headers are only trusted from real Cloudflare edges and local reverse proxies, so attackers cannot fake their IP to dodge a lockout.
- Site-Wide Firewall — Switches on automatically when you connect. Every public request is checked against IPs, VPNs, Tor nodes and datacenters seen attacking the ZeroBot network, with optional country rules. If ZeroBot is slow to answer, the visitor is let through after 3 seconds.
- Browser Fingerprint — Detects headless browsers, VMs and automation frameworks.
- Comment Guard — Blocks bot comments before they are saved.
- REST API Guard — Screens public REST calls, with configurable exempt routes.
- Shared blacklist — IPs locked out by the login guard are pushed to your ZeroBot blacklist and blocked on every site you connect.
- Domain Rules — Create, edit, and delete antibot rules from inside wp-admin.
- Whitelist — IPs, CIDR ranges, and ASNs scoped per service. Bulk import supported.
- Blacklist — Same scoping and bulk import as the whitelist.
- Threat Logs — Filterable, paginated viewer of every traffic event with CSV export.
- Dashboard — Live stats, 7-day traffic chart, recent threats, account info.
- Cloudflare and reverse-proxy IP detection that cannot be spoofed by visitors
- Decision cache via WordPress object cache (Redis/Memcached) with transient fallback
- Fail-open by default — never breaks your site if the API is unreachable
- Daily license verification via wp-cron
- WP-admin dashboard widget showing bots/humans (24h)
- Pure PHP + vanilla JS — no jQuery, no React, no external CDN
安装:
- Install from Plugins → Add New (search "ZeroBot Security"), or upload the zip.
- Activate the plugin. Login protection and the XML-RPC kill switch are on right away.
- Optional: open ZeroBot → Dashboard and, under "Turn on network protection", enter the email of an administrator of this site and click "Start free trial" (7 days, 100 IP checks, no card). Click the link in the activation email: the site connects and the firewall switches on. Already have a ZeroBot license key? Paste it under ZeroBot → License.
- Adjust the layers in ZeroBot → Protection.
常见问题:
Do I need an account?
No. Login brute-force protection and the XML-RPC kill switch work right after activation, with no account and no data leaving your site. An account is only needed for network protection.
What happens when my trial ends?
Network protection pauses and the free protections keep running. If you activate a plan later, the plugin notices within a day (or immediately with "Check again") and switches it back on.
I use Cloudflare or another proxy. Will lockouts hit the right IP?
Cloudflare and local reverse proxies (for example nginx in front of Apache) are detected automatically. Behind another CDN, enable "Trust proxy headers" in Protection Settings and check "Your detected IP" on the License page.
I use Jetpack. Is XML-RPC still blocked?
No. Jetpack connects to WordPress.com through XML-RPC, so the kill switch stands down while Jetpack is active. Login protection still runs.
Will this plugin break my site if the ZeroBot API is down?
No. The default Fail Mode is "Fail Open" — visitors are allowed through silently and the incident is logged to the PHP error log. You can switch to Fail Closed in Protection Settings if you prefer strict security.
How much does it call the ZeroBot API?
Every visitor decision is cached per-IP for 24 hours by default, so repeat visitors do not trigger additional API calls. A page that gets 1,000 hits/hour from returning visitors typically results in only a handful of API calls.
Does the fingerprint collector always run?
No. The fingerprint collector is disabled by default and only injects on the public site when the administrator turns on "Browser Fingerprint" under Protection Settings.
Does it work with WooCommerce?
Yes — the REST API Guard auto-exempts /wc/store/ routes. Add other custom routes to the
exempt list as needed.
Does it support multisite?
Single-site only for now.
更新日志:
1.1.1
- Security: a ZeroBot account can only be created from the plugin with the email of an administrator of the site. ZeroBot also confirms this with the site during signup.
- New: free protection without an account. The Login Brute-Force Guard and the XML-RPC kill switch now run as soon as the plugin is active. Previously every protection waited for a license key, so new installs protected nothing.
- New: create a ZeroBot trial account from inside wp-admin. Enter an email, confirm it, and the plugin activates itself. Pasting an existing license key still works.
- New: free dashboard with 7-day counts of failed logins, lockouts and blocked XML-RPC requests.
- New: when a plan or trial ends, network protection pauses with a clear notice and the free layer keeps running. A daily check re-enables it automatically after renewal.
- Security: visitor IP detection no longer trusts proxy headers sent by the visitor. CF-Connecting-IP is only accepted from Cloudflare edges, and X-Real-IP / X-Forwarded-For only from local reverse proxies or when "Trust proxy headers" is enabled. Forged headers could previously bypass the login lockout or lock out someone else's IP. The old default of trusting all proxy headers is switched off on update.
- Fix: a temporary API outage during the daily license check no longer switches network protection off until the next day.
- Fix: the XML-RPC kill switch stands down while Jetpack is active.
- Fix: a visitor flagged as a bot was kept blocked for 24 hours, even after being whitelisted. Bot verdicts are now cached for 15 minutes, and whitelisting an IP from the plugin applies immediately.
- Change: the Site-Wide Firewall is on by default and switches on whenever a site is connected.
- Change: without a valid license, the network layers (firewall, browser fingerprint, comment and REST API guards, shared blacklist) are shown off and cannot be switched on.
- Fix: the firewall now gives up after 3 seconds with no retries if the API is slow (it could previously hold a page for up to 24 seconds before failing open).
- Fix: when the trial checks are used up or the plan ends, the firewall pauses its API calls for an hour instead of calling on every page view, and the dashboard explains why.
- Fix: the master protection switch is on for new installs. On update it is turned on only for sites that never saved the settings page.
- Tested with WordPress 7.1.
- New: searchable multi-country picker on the Protection Settings page. Replaces the plain-text "Allowed Countries" input with a chip-based UI that lists all 249 ISO countries with flag emoji, alphabetical search, and a clear "Allow all / Only specific" mode toggle.
- Fix: visitors blocked by country policy now correctly show a yellow "Denied" badge on the Dashboard's Recent Activity widget. They were previously stacked into the red "Bot" bucket even though the block reason was "Country Denied (XX)".
- Fix: country flags now render in both the Dashboard widget and the
Threat Logs table. The flag helper expects a 2-letter ISO code, but the
API ships the country as a name -- so flags silently failed for every
row. A new
Helpers::countryNameToCode()lookup resolves names to codes, and the flag image renders before the country name on every log row. - Change: removed the Score column from the Dashboard Recent Activity widget and the Threat Logs table. The Reason already explains why a request was flagged, and the numeric score added visual noise without decision-relevant information.
- Security: tightened the firewall verdict cache to bot-only. Clean verdicts are no longer cached, so an IP that turns malicious mid-cache doesn't keep passing through for up to 24 hours. Bot verdicts continue to be cached for instant re-blocking.
- Compliance:
$_SERVER['REQUEST_URI']inXmlRpcGuard::register()is now run throughwp_unslash()andsanitize_text_field()before the regex match, clearing the two PHPCS warnings about that variable.
- Fix: critical error on every wp-admin page caused by a missing
License::isDomainAuthorized()method that theadmin_noticeshook called. The method now exists on the License class, fails open when no authorization state has been recorded yet, and gets set true/false byactivate()based on whether the auto domain-registration call to the ZeroBot platform succeeded (HTTP 200) or reported the domain as already registered (HTTP 409).
- WordPress.org review compliance: removed the broken
flagpedia.net/privacyURL from the External Services section of readme.txt. - The chart-data bootstrap on the admin dashboard now ships via
wp_add_inline_script()attached to the existingzerobot-security-adminhandle, instead of an inline<script>tag. No behavioural change — the same JS payload is delivered through the official WordPress enqueue API.
- WordPress.org review compliance: replaced the short "zb_" prefix everywhere it appeared in PHP and JS (AJAX action names, option keys, transient keys, nonce names, cron hooks, JS globals, custom DB table names, WP_Error codes, and the admin script handle) with the full "zerobot_security_" prefix so every plugin-defined identifier is at least the WP.org-required 4 characters and is uniquely namespaced.
- No functional or UI changes — the rename is purely cosmetic (CSS class names beginning with "zb-" are stylesheet-internal and were left unchanged, since they don't conflict with WordPress core or other plugins).
- Second Plugin Check compliance pass: final 3 errors resolved (wrap countryFlagImg() output in wp_kses(); add translators comment for "Cleared %d cached decisions"; etc.). Input-sanitization warnings addressed across Helpers, Firewall, ProtectionSettings, LicensePage.
- Fingerprint script now passes the plugin version to wp_enqueue_script() for reliable cache-busting.
- Uninstall variables renamed to zerobot_security_* prefix.
- Full Plugin Check compliance pass: wrap every Helpers::icon() SVG output through wp_kses() with a tight SVG tag allowlist; add wp_unslash() + sanitize calls on every $_SERVER / $_POST / $GET read; gate error_log() behind WP_DEBUG; replace date() with gmdate(); rename plugin constants to ZEROBOT_SECURITY* prefix; drop load_plugin_textdomain (WP 4.6+ auto-loads translations); add translators comments for all placeholders; LoginGuard queries use esc_sql() for the table identifier; uninstall uses prefixed variables and prepared statements.
- Fingerprint script now enqueued via
wp_enqueue_script()with ascript_loader_tagfilter for the data attributes, replacing the rawecho '<script>'. Respects standard WordPress script filters. - DecisionCache::flush() no longer issues a raw LIKE query — iterates the
matching transient option names and calls
delete_transient()for each, so the object cache and transient DB stay in sync. - Threat Logs are now always scoped to the current WordPress site's host (the "Domain" filter is removed — it's redundant and could leak cross-domain data).
- Firewall self-heals domain-deauthorization in real time: the plugin flags the site immediately on the first failed API call instead of waiting for the daily verify cron, so the warning banner shows up right after the admin removes the domain from authorized_domains.
- Admin warning banner is now shown on every wp-admin page, not only the plugin's own screens.
- Country flags in the Dashboard and Threat Logs render as reliable PNG images (via flagcdn.com) instead of Unicode emoji, which some platforms don't render.
- Per-IP decision cache extended to 24 hours to reduce API load
- Allowed-countries enforcement moved server-side so denied requests are logged correctly
- Login verification (device 2FA) toggle added per user
- Browser Fingerprint layer now also injects on wp-login.php and via wp_footer fallback
- Fingerprint collector no longer skipped for logged-in users (configurable)
- "Country Denied" badge styled distinctly from generic bot block
- Threat Logs show the visitor path alongside IP / ISP / country
- /v3/openapi now receives allowed_countries from the plugin so geo-blocks are enforced server-side and logged with the correct reason
- Decision caching logic refactored so every request logs correctly
- Fingerprint injection improvements
- "Clear Threats for this Domain" action in Threat Logs
- "Path" column in Threat Logs showing the URL the visitor accessed
- Initial release
- Full Dashboard, License, Rules, Whitelist, Blacklist, Protection Settings, Threat Logs
- Six protection layers: Page, Firewall, Login, Comment, REST API, XML-RPC
- Decision caching with object cache + transient fallback
- CSV export for threat logs
- WP-admin dashboard widget
- Cloudflare / proxy IP detection