WordPress security changelog
MEDIUM CVE-2014-9460 Modified

Wp Vipergb: Cross-site scripting

Wp Vipergb is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

CVE / CNA score 6.8 CVSS · cve@mitre.org
NVD score 6.8 CVSS 2.0 · nvd@nist.gov
Component
Wp Vipergb
Plugin slug
wp-vipergb
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Jan 02, 2015
Weakness
CWE-352 — Cross-Site Request Forgery (CSRF)

This CVE was published Jan 02, 2015 and is one of 3 known issues for this plugin.

What to do

Update, patch or deactivate.

Update Wp Vipergb to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

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.

NVD vector: AV:N/AC:M/Au:N/C:P/I:P/A:P

References

Primary and upstream sources