WP-Ban Security & Risk Analysis

wordpress.org/plugins/wp-ban

Ban users by IP, IP Range, host name, user agent and referrer url from visiting your WordPress's blog.

9K active installs v1.69.2 PHP + WP 4.3+ Updated Mar 9, 2025
banbanneddenieddenypermission
91
A · Safe
CVEs total2
Unpatched0
Last CVEDec 6, 2022
Safety Verdict

Is WP-Ban Safe to Use in 2026?

Generally Safe

Score 91/100

WP-Ban has a strong security track record. Known vulnerabilities have been patched promptly. It's a solid choice for most WordPress installations.

2 known CVEsLast CVE: Dec 6, 2022Updated 1yr ago
Risk Assessment

The wp-ban plugin v1.69.2 exhibits a mixed security posture. On the positive side, it demonstrates good practices by exclusively using prepared statements for SQL queries, avoiding file operations and external HTTP requests, and checking for nonces and capabilities in some areas. However, a significant concern arises from its attack surface, specifically one unprotected AJAX handler. While taint analysis did not reveal any critical or high severity flows, and there are no known currently unpatched CVEs, the plugin has a history of medium severity vulnerabilities, including Cross-site Scripting and Improper Input Validation. This history, coupled with the unprotected AJAX endpoint, suggests a potential for insecure handling of user input that could be exploited.

Key Concerns

  • Unprotected AJAX handler
  • Low output escaping percentage (41%)
  • History of medium severity vulnerabilities
Vulnerabilities
2 published

WP-Ban Security Vulnerabilities

CVEs by Year

1 CVE in 2014
2014
1 CVE in 2022
2022
Patched Has unpatched

Severity Breakdown

Medium
2

2 total CVEs

CVE-2022-4260medium · 5.5Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

WP-Ban <= 1.69 - Authenticated (Administrator+) Stored Cross-Site Scripting

Dec 6, 2022 Patched in 1.69.1 (413d)
CVE-2014-6230medium · 5.3Improper Input Validation

WP-Ban < 1.64 - Improper Input Validation

Sep 17, 2014 Patched in 1.64 (3415d)
Version History

WP-Ban Release Timeline

Code Analysis
Analyzed Mar 16, 2026

WP-Ban Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
22
15 escaped
Nonce Checks
2
Capability Checks
1
File Operations
0
External Requests
0
Bundled Libraries
0

Output Escaping

41% escaped37 total outputs
Data Flows · Security
All sanitized

Data Flow Analysis

1 flows
<ban-options> (ban-options.php:0)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface
1 unprotected

WP-Ban Attack Surface

Entry Points1
Unprotected1

AJAX Handlers 1

authwp_ajax_ban-adminwp-ban.php:75
WordPress Hooks 3
actionplugins_loadedwp-ban.php:33
actionadmin_menuwp-ban.php:40
actioninitwp-ban.php:160
Maintenance & Trust

WP-Ban Maintenance & Trust

Maintenance Signals

WordPress version tested6.5.8
Last updatedMar 9, 2025
PHP min version
Downloads326K

Community Trust

Rating74/100
Number of ratings27
Active installs9K
Developer Profile

WP-Ban Developer Profile

Lester Chan

20 plugins · 888K total installs

71
trust score
Avg Security Score
88/100
Avg Patch Time
1377 days
View full developer profile
Detection Fingerprints

How We Detect WP-Ban

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about WP-Ban