CVE-2014-9460: Multiple cross-site request forgery (CSRF) vulnerabilities in the WP-ViperGB plugin before 1.3.11 for WordPres

Q: How do I fix CVE-2014-9460?

wp-vipergb: upgrade to newer than 1.3.10. Exact commands for each OS are on this page.

Q: Is CVE-2014-9460 being exploited?

CVE-2014-9460 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2014-9460 affect?

CVE-2014-9460 affects wp-vipergb. Severity is medium (CVSS 6.8). Multiple cross-site request forgery (CSRF) vulnerabilities in the WP-ViperGB plugin before 1.3.11 for WordPress allow remote attackers to hijack the authentication of administrators for requests that (1) change plugin settings via unspecifi

Q: How urgent is CVE-2014-9460?

Priority 46/100. Public exploit reference

This month

MEDIUM 6.8UPGRADE

CVE-2014-9460 is a medium-severity flaw (CVSS 6.8) affecting wp-vipergb. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Multiple cross-site request forgery (CSRF) vulnerabilities in the WP-ViperGB plugin before 1.3.11 for WordPress allow remote attackers to hijack the authentication of administrators for requests that (1) change plugin settings via unspecified vectors or conduct cross-site scripting (XSS) attacks via the (2) vgb_page or (3) vgb_items_per_pg parameter in the wp-vipergb page to wp-admin/options-general.php.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.8 (Medium)
EPSS exploit chance	1.2% (top 33%)
CISA exploited list	No
Weakness	CWE-352
Published	2015-01-02
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: justin klein

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2015-01-02 20:59 UTCPublished CVE record published
2026-06-17 00:18 UTCUpdated Record last modified

justin klein wp-vipergb UPGRADE

Affected: <= 1.3.10

Fixed in: newer than 1.3.10

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-vipergb || rpm -q wp-vipergb || wp-vipergb --version

2. UPGRADE to newer than 1.3.10 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wp-vipergb

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-vipergb

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2014-9460?

wp-vipergb: upgrade to newer than 1.3.10. Exact commands for each OS are on this page.

Is CVE-2014-9460 being exploited?

CVE-2014-9460 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2014-9460 affect?

CVE-2014-9460 affects wp-vipergb. Severity is medium (CVSS 6.8). Multiple cross-site request forgery (CSRF) vulnerabilities in the WP-ViperGB plugin before 1.3.11 for WordPress allow remote attackers to hijack the authentication of administrators for requests that (1) change plugin settings via unspecifi

How urgent is CVE-2014-9460?

Priority 46/100. Public exploit reference

Software pages

WordPress vulnerabilities · PHP vulnerabilities

Related CVEs

CVE-2015-9356 MEDIUM 6.1 UPGRADE The wp-vipergb plugin before 1.3.16 for WordPress has XSS via add_query_arg() and remove_query_arg(), a differ

References

← Back to latest CVEs