supersoju

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.
<ul>
<li>Block IPs via Cloudflare after X failed login attempts</li>
<li>Block IPs that generate excessive 404 responses (bots and scanners)</li>
<li>Block IPs attacking via XML-RPC with intelligent detection</li>
<li>Automatic unblocking after a configurable duration</li>
<li>Whitelist IPs to never block or track them (supports IPv6 CIDR ranges)</li>
<li>View and manually unblock blocked IPs from the admin</li>
<li>Block source tracking — see whether each IP was blocked via login, XML-RPC, or 404</li>
<li>Sync existing Cloudflare blocks into the local blocked IPs list</li>
<li>Secure settings page with Cloudflare API token validation</li>
<li>Hourly cron job for automatic maintenance</li>
</ul>
<h3>External Services</h3>
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:
<ol>
<li>
During settings validation (when you save Cloudflare credentials):
<ul>
<li>Your Cloudflare API token (for verification)</li>
<li>Endpoint: <code>https://api.cloudflare.com/client/v4/user/tokens/verify</code></li>
</ul>
</li>
<li>
When blocking an IP (after a threshold is reached):
<ul>
<li>The IP address to be blocked</li>
<li>Your Cloudflare email address and API key/token</li>
<li>Your Cloudflare Zone ID</li>
<li>A note describing the reason for the block</li>
<li>Endpoint: <code>https://api.cloudflare.com/client/v4/zones/{zone_id}/firewall/access_rules/rules</code></li>
</ul>
</li>
<li>
When syncing from Cloudflare (on demand):
<ul>
<li>Fetches existing firewall rules from your Cloudflare zone</li>
<li>Endpoint: <code>https://api.cloudflare.com/client/v4/zones/{zone_id}/firewall/access_rules/rules</code></li>
</ul>
</li>
</ol>
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.
<h3>License</h3>
GNU General Public License v2 or later

Block Logins with Cloudflare

Block brute-force login attempts by integrating with Cloudflare's firewall to automatically block IPs after failed logins.

Pascal CESCATO

Stop XML-RPC Attacks protects your WordPress site from XML-RPC brute force attacks, DDoS attempts, and reconnaissance probes while maintaining compatibility with essential services like Jetpack and WooCommerce.
Features:
<ul>
<li>Three security modes: Full Disable, Guest Disable, or Selective Blocking</li>
<li>Blocks dangerous methods: system.multicall, pingback.ping, and more</li>
<li>Compatible with Jetpack and WooCommerce</li>
<li>Optional user enumeration blocking</li>
<li>Attack logging for monitoring</li>
<li>Zero configuration required – works out of the box</li>
<li>Clean, intuitive admin interface</li>
</ul>

Stop XML-RPC Attacks

Blocks dangerous XML-RPC methods while preserving Jetpack, WooCommerce, and mobile apps compatibility.

Block Logins with Cloudflare vs Stop XML-RPC Attacks