WP-ViperGB
wp-vipergb · plugin
Known security vulnerabilities for WP-ViperGB. Find out in seconds which version runs on your site with WP Lens.
3 known vulnerabilities
2 exploitable without logging in · latest May 23, 2024
Listed on wordpress.org · latest 1.6.2 · last updated May 23, 2024 · 300+ installs
Not updated since May 23, 2024. A component left without updates for over two years should not be expected to patch new vulnerabilities.
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- Medium 6.8
Multiple cross-site request forgery (CSRF) vulnerabilities in the WP-ViperGB plugin before 1.3.11 for WordPress allow remote attackers to hi
- Medium 6.1
CVE-2015-9356unauthenticated · needs a click
The wp-vipergb plugin before 1.3.16 for WordPress has XSS via add_query_arg() and remove_query_arg(), a different issue than CVE-2014-9460.
- Medium 4.3
CVE-2024-4409unauthenticated · needs a click≤ 1.6.1
WP-ViperGB <= 1.6.1 - Cross-Site Request Forgery
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).