| 开发者 | ipabuse |
|---|---|
| 更新时间 | 2026年11月21日 03:19 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
/wp-content/plugins/ipabuse-firewall directory, or install the plugin through the WordPress plugins screen directly.Yes. You need a free ipabuse.org account and API key to fetch the blocklist and submit reports.
When "Report Failed Logins" is enabled (on by default), the plugin automatically reports: failed wp-login.php/XML-RPC login attempts (BRUTE_FORCE), comment spam (SPAM), and sustained bursts of requests for nonexistent pages (SCANNING). Each report includes the IP address, category, and a generic description — the attempted username is never included. Private/loopback IP ranges, and any IP on your allowlist, are never reported. Disable the "Report Failed Logins" option on the plugin's Settings page to turn off all automatic reporting. You can also manually block or report any IP from the IP Lookup page or via WP-CLI, independent of this setting.
No. Private and loopback IP ranges are never blocked or reported.
wp ipabuse clear-cache CLI command — to flush the plugin's cache on demand (e.g. after restoring a database backup).$wpdb->prepare()'s %i identifier placeholder instead of raw string interpolation.wp ipabuse block|report CLI commands.IPAbuse_Reporter::report_abuse()) used by every detector and by the new manual actions, instead of duplicating gating/dedup logic per feature.blocked_at index to the blocked-IPs table — it's used in sorting/filtering on the Blocked IPs page, the dashboard sparkline, and retention cleanup, and was previously unindexed.is_blocked() is now cached per-IP for 60 seconds (invalidated on block/unblock), cutting repeat database hits on sites running a persistent object cache (Redis/Memcached) — most valuable exactly when it matters most: sustained traffic from an actively-blocked IP.blocked_at index, so the index would have silently never applied on sites that had already run the 1.4.1 upgrade. Fixed.wp ipabuse sync now run the exact same full sync routine as the 15-minute cron (prune missing/expired, apply country blocklist) instead of a partial subset of it.country column / block-history table were introduced never received that schema change, since register_activation_hook() only fires on activate/reactivate, not on a simple file update. This silently broke new blocks and the Blocked IPs/Dashboard listings (visible as a blocked-IP count that stopped updating) while dbDelta()-based inserts failed. Fixed with a version-gated upgrade check on plugins_loaded that self-heals the schema automatically — no manual action needed.wp ipabuse block|unblock|sync|status WP-CLI commands.xmlrpc_login_error), using the same reporting/local-rate-limit path as wp-login.php.GET /wp-json/ipabuse-firewall/v1/status) for external monitoring, gated by the manage_options capability.X-Forwarded-For from trusted IP sources to prevent spoofing.