Wp-ban
4 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Wp-ban, a product in the web cms plugins space. Use it to gauge the current risk picture and drill into individual advisories.
Wp-ban CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 0 |
| 2026-04 | 0 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 0 |
Severity
How the 4 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- Medium2
- Low2
Latest CVEs
The 4 most recently published vulnerabilities affecting Wp-ban.
- CVE-2022-4260WP-Ban < 1.69.1 - Admin+ Stored XSS4.8
- CVE-2022-4631WP-Ban ban-options.php cross site scripting3.5
- CVE-2021-4252WP-Ban ban-options.php toggle_checkbox cross site scripting3.5
- CVE-2014-6230WP-Ban plugin before 1.6.4 for WordPress, when running in certain configurations, allows remote attackers to bypass the IP blacklist via a crafted X-Forwarded-For header.4.3
Product grouping is registry-driven, with AI assist and human review. How it works