Contact Bank – Contact Form Builder for WordPress <= 2.0.69 - Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.0.70
- Affected Plugin
- Contact Bank – Contact Form Builder for WordPress
- Affected Version
<= 2.0.69- CVSS
- 7.2High
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2014-8807
At a glance
CVE-2014-8807 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Contact Bank WordPress plugin, affecting versions <= 2.0.69. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.0.70; sites on affected versions should update now. Disclosed November 2014, reported by Kacper Szurek.
Vulnerability Overview
The Contact Bank – Contact Form Builder for WordPress for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘ux_dropdown’ and ‘ux_checkbox’ parameter in versions up to, and including, 2.0.69 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Contact Bank <= 2.0.69 carries this weakness at ux_dropdown, and reaching it 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 Contact Bank the fix is 2.0.70: builds <= 2.0.69 are affected, anything from 2.0.70 onward is not.
Remediation
Update to version 2.0.70, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Contact Bank: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Contact Bank 2.0.70 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Contact Bank – Contact Form Builder for WordPress
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C