Beschreibung
Block Logins with Cloudflare helps protect your WordPress site from brute-force attacks by blocking IPs at the Cloudflare firewall after a configurable number of failed login attempts.
- Block IPs via Cloudflare after X failed login attempts
- Block IPs that generate excessive 404 responses (bots and scanners)
- Block IPs attacking via XML-RPC with intelligent detection
- Automatic unblocking after a configurable duration
- Whitelist IPs to never block or track them (supports IPv6 CIDR ranges)
- View and manually unblock blocked IPs from the admin
- Block source tracking — see whether each IP was blocked via login, XML-RPC, or 404
- Secure settings page with Cloudflare API token validation
- Hourly cron job for automatic maintenance
External Services
This plugin relies on the Cloudflare API to function. It communicates with Cloudflare’s external servers to block IP addresses at the firewall level.
What is the Cloudflare API and what is it used for?
The Cloudflare API is a RESTful service provided by Cloudflare, Inc. that allows programmatic management of Cloudflare firewall rules. This plugin uses it to automatically block and unblock IP addresses based on failed login attempts, XML-RPC attacks, and 404 scanning activity.
What data is sent and when?
The plugin sends the following data to Cloudflare’s API servers:
-
During settings validation (when you save Cloudflare credentials):
- Your Cloudflare API token (for verification)
- Endpoint:
https://api.cloudflare.com/client/v4/user/tokens/verify
-
When blocking an IP (after a threshold is reached):
- The IP address to be blocked
- Your Cloudflare email address and API key/token
- Your Cloudflare Zone ID
- A note describing the reason for the block
- Endpoint:
https://api.cloudflare.com/client/v4/zones/{zone_id}/firewall/access_rules/rules
No personally identifiable information about your WordPress users is transmitted. Only IP addresses are sent to Cloudflare.
Service provider information:
– Service: Cloudflare API
– Provider: Cloudflare, Inc.
– Terms of Service: https://www.cloudflare.com/terms/
– Privacy Policy: https://www.cloudflare.com/privacypolicy/
– API Documentation: https://developers.cloudflare.com/api/
Required for functionality:
This plugin requires a Cloudflare account and will not function without valid Cloudflare API credentials. The external API calls are essential to the plugin’s core functionality.
License
GNU General Public License v2 or later
Installation
- Upload the plugin files to the
/wp-content/plugins/block-logins-cfdirectory, or install through the WordPress plugins screen. - Activate the plugin through the ‚Plugins‘ screen.
- Go to Block Logins CF in the admin sidebar to configure your Cloudflare credentials and settings.
FAQ
-
What permissions does my Cloudflare API token need?
-
Your token needs
Zone.ZoneandZone.Firewallpermissions for the relevant zone. -
Where do I find my Cloudflare Zone ID?
-
In your Cloudflare dashboard, select your domain and look for the Zone ID in the Overview tab.
-
Does this block at the Cloudflare level or just WordPress?
-
This plugin blocks IPs at the Cloudflare firewall, stopping attacks before they reach your server.
-
What does 404 blocking protect against?
-
It detects bots and vulnerability scanners that probe your site by requesting many non-existent URLs. When an IP exceeds the configurable 404 threshold, it is blocked via Cloudflare just like a brute-force login attacker.
Rezensionen
Zu diesem Plugin liegen noch keine Rezensionen vor.
Mitwirkende und Entwickler
„Block Logins with Cloudflare“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin mitgewirkt:
Mitwirkende
Übersetze „Block Logins with Cloudflare“ in deine Sprache.
Interessiert an der Entwicklung?
Durchstöbere den Code, sieh dir das SVN-Repository an oder abonniere das Entwicklungsprotokoll per RSS.
Änderungsprotokoll
1.1
- Added 404-based IP blocking to detect and block bots and vulnerability scanners
- Added XML-RPC protection with intelligent attack detection
- Added block source tracking — blocked IPs now show whether they were blocked via login, XML-RPC, or 404
- Added 404 activity log in the Blocked IPs admin page
- Added IPv6 CIDR range support in the IP whitelist
- Added caching for Cloudflare API token validation to prevent throttling
1.0
- Initial release