Skip to content
PluginCanary

WP-Ban

by Lester Chan · 8,000+ active installs · Checked 3 Nov 2026
Healthy

Healthy: WP-Ban is maintained, has no open risk signals and no unpatched vulnerabilities.

91/ 100 Canary Score
Sub-scores for WP-Ban
Ownership100
Maintenance100
Security100
Support70
Reputation70

How the score works

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
GamerZ21 Jan 2007 to 9 Aug 2026, 149 commits

1 committer recorded. No ownership changes recorded since 3 Nov 2026.

Maintenance

Last release
3 months ago
Releases, 24 months
2
Tested up to
7.0 vs 7.1
Requires PHP
8.2 supported 8.2+
Releases per quarter for WP-Ban
Q1 20240
Q2 20240
Q3 20240
Q4 20240
Q1 20251
Q2 20250
Q3 20250
Q4 20250
Q1 20260
Q2 20260
Q3 20261
Q4 20260

Last release 9 Aug 2026. Tested up to 7.0, 1 major version behind WordPress 7.1.

Support

Support history appears after our first snapshots of the forum counts.

Security record

PublishedIssueCVSSAffectedFixed inDays to patch
6 Dec 2022WP-Ban <= 1.69 - Authenticated (Administrator+) Stored Cross-Site Scripting5.5<= 1.691.69.1246
17 Sep 2014WP-Ban < 1.64 - Improper Input Validation5.3< 1.641.640

Source: Wordfence Intelligence.

Reputation

Lifetime rating 3.7 from 27 ratings. Quarterly trends appear as new reviews arrive.

Rating distribution
5 star16
4 star2
3 star0
2 star2
1 star7

Momentum

8,000+ active installs. History builds with each weekly snapshot.

Weekly downloads, last 27 weeks
Weekly downloads for WP-Ban
4 May 202649
11 May 2026103
18 May 202695
25 May 2026101
1 Jun 2026148
8 Jun 2026178
15 Jun 202697
22 Jun 202679
29 Jun 202697
6 Jul 202691
13 Jul 2026106
20 Jul 2026122
27 Jul 2026140
3 Aug 2026747
10 Aug 20261,587
17 Aug 2026398
24 Aug 2026309
31 Aug 2026262
7 Sep 2026239
14 Sep 2026249
21 Sep 2026223
28 Sep 2026274
5 Oct 2026218
12 Oct 2026235
19 Oct 2026623
26 Oct 2026410
2 Nov 202643

Weekly downloads over the last 4 weeks are 23% above the 27-week average.

Healthier alternatives

Same category, higher Canary Score. Never sponsored.

IP Location BlockScore 96 · 10,000+Wordfence Security - Firewall, Malware Scan, and Login SecurityScore 94 · 5,000,000+Sucuri Security - Auditing, Malware Scanner and Security HardeningScore 93 · 600,000+WP Content Copy Protection & No Right ClickScore 93 · 100,000+NinjaFirewall (WP Edition) - Advanced Security Plugin and FirewallScore 93 · 100,000+

Facts

Version2.0.0
AuthorLester Chan
Added21 Jan 2007
Last updated9 Aug 2026
Active installs8,000+
Requires WordPress6.8
Tested up to7.0.8
Requires PHP8.2
CategorySecurity & Privacy > Security Scanning & Malware Protection
Tagsip, ban, bots, hostname, referrer

Other plugins by this author: WP-PageNavi, WP-Sweep, WP-PostViews, WP-DBManager, WP-Polls, WP-PostRatings, WP-ServerInfo, WP-UserOnline, WP-ShowHide, WP-Print, WP-DownloadManager, WP-Stats

Questions

Is WP-Ban still maintained?

WP-Ban was last updated on 9 Aug 2026. Its Canary status is Healthy.

Is WP-Ban safe?

WP-Ban has no open unpatched vulnerabilities on record. 0 vulnerabilities were published in the last 24 months. Its Canary status is Healthy.

Who owns WP-Ban?

The wordpress.org author is Lester Chan. Recent committers: GamerZ, matt. We have recorded no ownership change.

What can I use instead of WP-Ban?

Plugins in the same category with a higher Canary Score: IP Location Block, Wordfence Security - Firewall, Malware Scan, and Login Security, Sucuri Security - Auditing, Malware Scanner and Security Hardening, WP Content Copy Protection & No Right Click, NinjaFirewall (WP Edition) - Advanced Security Plugin and Firewall.

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