wp-ban vulnerabilities and fixes
Recent CVEs affecting wp-ban, with upgrade or downgrade steps. 3 tracked.
Also searched as: wp ban.
wp-ban has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2023-01-02. Highest priority: CVE-2022-4260 (score 36/100).
- CVE-2022-4631 LOW 3.5 MITIGATE A vulnerability, which was classified as problematic, was found in WP-Ban
- CVE-2022-4260 MEDIUM 4.8 UPGRADE The WP-Ban WordPress plugin before 1.69.1 does not sanitise and escape some of its settings, which could allow
- CVE-2021-4252 LOW 3.5 UPGRADE A vulnerability, which was classified as problematic, has been found in WP-Ban
FAQ
How do I fix wp-ban vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is wp-ban being exploited right now?
None of the tracked wp-ban CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which wp-ban CVE should I patch first?
CVE-2022-4260 currently ranks highest (36/100): The WP-Ban WordPress plugin before 1.69.1 does not sanitise and escape some of its settings, which could allow.