VS Contact Form <= 11.5 - Reflected Cross-Site Scripting
Strategic Overview
- Status
- Patched in 11.6
- Affected Plugin
- VS Contact Form
- Affected Version
<= 11.5- CVSS
- 6.1Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE pending
At a glance
This record tracks a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the VS Contact Form WordPress plugin, affecting versions <= 11.5. 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 11.6; sites on affected versions should update now. Disclosed May 2022.
Vulnerability Overview
The VS Contact Form plugin for WordPress may be vulnerable to Reflected Cross-Site Scripting via the $_SERVER['REQUEST_URI'] parameter in versions up to, and including, 11.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a victim into performing an action such as clicking on a link. Only victims using older browser should be impacted as newer browsers urlencode the REQUEST_URI parameter by default
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')
VS Contact Form <= 11.5 carries this weakness at REQUEST_URI, 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 VS Contact Form the fix is 11.6: builds <= 11.5 are affected, anything from 11.6 onward is not.
Remediation
Update to version 11.6, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to VS Contact Form: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: VS Contact Form 11.6 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