Is wp-vipergb (WordPress plugin) vulnerable?

WordPress wp-vipergb has 2 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

2advisories

0critical

0on CISA KEV

1no fix recorded

CVE	Title	Severity	CVSS	Affected	Fixed in
CVE-2014-9460	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.8	`<=1.3.10`	–
CVE-2015-9356	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	6.1	`<1.3.16`	`1.3.16`

Am I affected?

Find out in one command. phpwarden checks your WordPress install against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden wordpress /var/www/html

Or keep it checked automatically with the GitHub Action or a nightly cron; see WordPress docs.

Install docs How findings are ranked

A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.