Contact Form Plugin <= 4.0.1 - Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 4.0.2
- Affected Plugin
- Contact Form Plugin
- Affected Version
<= 4.0.1- CVSS
- 6.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2017-20055
At a glance
CVE-2017-20055 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Contact Form Plugin WordPress plugin, affecting versions <= 4.0.1. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). The issue is fixed in version 4.0.2; sites on affected versions should update now. Disclosed March 2017, reported by Julien Rentrop.
Vulnerability Overview
A vulnerability classified as problematic has been found in BestWebSoft Contact Form Plugin 4.0.0. This affects an unknown part. The manipulation leads to basic cross site scripting (Stored). It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 4.0.2 is able to address this issue. It is recommended to upgrade the affected component.
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 interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Contact Form Plugin <= 4.0.1 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 Form Plugin the fix is 4.0.2: builds <= 4.0.1 are affected, anything from 4.0.2 onward is not.
Remediation
Update to version 4.0.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Contact Form Plugin: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Contact Form Plugin 4.0.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C