Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

wp-vipergb vulnerabilities and fixes

Recent CVEs affecting wp-vipergb, with upgrade or downgrade steps. 1 tracked.

Also searched as: wp vipergb.

wp-vipergb has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2019-08-28. Highest priority: CVE-2015-9356 (score 37/100).

FAQ

How do I fix wp-vipergb 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-vipergb being exploited right now?

None of the tracked wp-vipergb CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which wp-vipergb CVE should I patch first?

CVE-2015-9356 currently ranks highest (37/100): The wp-vipergb plugin before 1.3.16 for WordPress has XSS via add_query_arg() and remove_query_arg(), a differ.

← Back to latest CVEs