Block wp-login
Block wp-login has one disclosed vulnerability in the WordSec catalog, all reported in 2019; it is fixed as of September 2026. Their average CVSS score is 8.8, and the most serious one scores 8.8 out of 10. Severity breakdown: 0 critical and 1 high.
The most common weakness is Cross-Site Request Forgery (CSRF), behind 1 of the records (100%).
The one issue recorded for Block wp-login has a vendor fix available, so running the current release closes it.
Block wp-login is installed on roughly 600 WordPress sites, so each unpatched flaw has a wide blast radius. The current release is tested up to WordPress 7.1.
Block WP Login <= 1.3.0 - Cross-Site Request Forgery
Read the full analysisVulnerability Records

Block wp-login
Author
Oliver Campion
Block wp-login.php and use a secret login URL Block wp-login prevents automated requests from reaching the default WordPress login endpoint. It creates a secret login URL for authorised users and adds Apache rewrite rules that return a 403 Forbidden response for direct requests to wp-login.php. Because blocked requests are rejected before WordPress loads, the plugin can reduce the server resources consumed by bots repeatedly targeting wp-login.php. Features include: Choose your own secret login slug or generate a random one. Block direct access to the default wp-login.php endpoint with a 403 response. Continue to support password resets, registration and WordPress administration email verification through the secret login URL. Rebuild the secret login file after a WordPress core update. Optionally email administrators when the login URL changes. Optionally notify the site owner when an administrator signs in from an IP address that is not on the known-IP list. Important compatibility information Block wp-login requires an Apache web server with mod_rewrite and a writable .htaccess file in the WordPress root directory. It is not compatible with Nginx or servers that do not honour .htaccess rules. Hiding the default login endpoint reduces automated login traffic, but it is not a replacement for strong passwords, two-factor authentication, updates, backups or other appropriate security controls.
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C