WP-Ban · Security record
Is WP-Ban safe?
No known vulnerability affects the current version (2.0.0). 4 issues were found in earlier versions and fixed, the latest disclosed on Dec 21, 2022.
Checked 2 days ago against the WPVulnerability database, for version 2.0.0.
How it’s looked after
- Last release
- Aug 9, 2026 (2 months ago)
- Releases in the last year
- 1
- Tested up to
- WordPress 7.0.8
- Active installs
- 8K+
4 known vulnerabilities
- 3 medium
- 1 not rated
None affects the current version.
Disclosed each year
- 20141
- 20223
Every known vulnerability in WP-Ban
Newest first, with any that affect the current version at the top.
- medium
Cross-site Scripting
Fixed in 1.69.1 · CVE-2022-4631 · Dec 21, 2022 · CVE
- medium
Improper Neutralization
Fixed in 1.64 · CVE-2021-4252 · Dec 18, 2022 · CVE
Fixed in 1.69.1 · CVE-2022-4260 · Dec 6, 2022 · Wordfence
Fixed in 1.64 · CVE-2014-6230 · Sep 4, 2014 · Wordfence
Questions about WP-Ban’s security
Is WP-Ban safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep WP-Ban updated: most attacks target sites that haven’t updated.
Does WP-Ban have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 4 older issues, fixed in earlier versions, so keep WP-Ban up to date.
Is WP-Ban still maintained?
Yes. Its last release was 2 months ago. No support threads were opened in the last two months.
Is WP-Ban compatible with the latest WordPress?
It’s tested up to WordPress 7.0.8, one version behind the current 7.1. Authors often update this line a few weeks after a release.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.