WP-ViperGB <= 1.3.10 - Cross-Site Request Forgery to Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.3.11
- Affected Plugin
- WP-ViperGB
- Affected Version
<= 1.3.10- CVSS
- 6.1Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2014-9460
At a glance
CVE-2014-9460 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WP-ViperGB WordPress plugin, affecting versions <= 1.3.10. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.3.11; sites on affected versions should update now. Disclosed December 2014, reported by Kenneth Jepsen.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in WP-ViperGB <= 1.3.10 takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For WP-ViperGB the fix is 1.3.11: builds <= 1.3.10 are affected, anything from 1.3.11 onward is not.
Remediation
Update to version 1.3.11, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP-ViperGB: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP-ViperGB 1.3.11 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WP-ViperGB
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C