Skip to content
PluginCanary

Block wp-login

by Oliver Campion · 600+ active installs · Checked 3 Nov 2026
Healthy

Healthy: maintained, last release 8 Oct 2026, 6 releases in 24 months, no unpatched vulnerabilities.

91/ 100 Canary Score
Sub-scores for Block wp-login
Ownership100
Maintenance100
Security100
Support70
Reputation70

How the score works

Quick answers

Is Block wp-login still maintained?
Yes. Last release 8 Oct 2026, 6 releases in the last 24 months. 8 Oct 2026 · wordpress.org
Who owns Block wp-login, and has it changed hands?
No change recorded. Main committer domainsupport since Apr 2017. 3 Nov 2026 · SVN log
Was Block wp-login removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is Block wp-login safe?
1 known vulnerability, fixed (latest in 1.3.2). Not on the exploited list. 27 Jun 2019 · Wordfence Intelligence
Is the latest Block wp-login update safe to install?
No ownership change before 1.5.9. No one-star spike after it. 8 Oct 2026 · Release history

Active signals

Facts we detected, with links to the source.

No open risk signals. Signals appear here when we detect an ownership change, closure, vulnerability or decline.

Ownership timeline

Who commits to the plugin's code on wordpress.org, over time.

Committers and their active periods
domainsupport9 Apr 2017 to 8 Oct 2026, 84 commits

1 committer recorded. No ownership change since 2017.

Maintenance

Last release
27 days ago
Releases, 24 months
6
Tested up to
7.1 current
Requires PHP
7.0 supported 8.2+
Releases per quarter
Releases per quarter for Block wp-login
Q1 20240
Q2 20240
Q3 20240
Q4 20240
Q1 20250
Q2 20251
Q3 20250
Q4 20251
Q1 20260
Q2 20261
Q3 20262
Q4 20261

Last release 8 Oct 2026. Tested with WordPress 7.1 (current).

Reputation

Last 90 days: no reviews. Lifetime: 4.7.

Rating distribution
5 star8
4 star0
3 star0
2 star1
1 star0

Security record

1 vulnerability on record, patched (latest fixed in 1.3.2).

Show 1 patched vulnerability
PublishedIssueCVSSAffectedFixed inDays to patch
27 Jun 2019Block WP Login <= 1.3.0 - Cross-Site Request Forgery8.8<= 1.3.01.3.2n/a

Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.

Support

100% of 1 support threads resolved in the last 2 months.

Momentum

600+ active installs. History builds with each weekly snapshot.

Momentum history builds with each snapshot.

Healthier alternatives

Same job, rated Healthy, higher Canary Score and at least 10,000 installs. Never sponsored.

No healthier plugin in the same category yet.

Facts

Version1.5.9
AuthorOliver Campion
Added7 Apr 2017
Last updated8 Oct 2026
Active installs600+
Requires WordPress5.0
Tested up to7.1.4
Requires PHP7.0
Categorynot stated
Tagssecurity, hide login, Brute Force, login security, custom login url

Other plugins by this author: Remove "Powered by WordPress", Options for Twenty Seventeen, Options for Twenty Twenty-One, Options for Twenty Twenty, SideMenu, Options for Twenty Nineteen, Display Remote Posts Block, Reset Customizer, Options for Block Themes, Deny All Firewall, Slidey Panel, Web:D Accounts

Questions

Is Block wp-login still maintained?

Yes. Last release 8 Oct 2026, 6 releases in the last 24 months.

Who owns Block wp-login, and has it changed hands?

No change recorded. Main committer domainsupport since Apr 2017.

Was Block wp-login removed from wordpress.org?

No. Listed on wordpress.org as of 3 Nov 2026.

Is Block wp-login safe?

1 known vulnerability, fixed (latest in 1.3.2). Not on the exploited list.

Is the latest Block wp-login update safe to install?

No ownership change before 1.5.9. No one-star spike after it.

Data: wordpress.org Plugins API, plugins SVN and Trac, wordpress.org reviews and support forum, Wordfence Intelligence, CISA KEV, NVD.Plugin data refreshed 3 Nov 2026.Report a data issue