WooCommerce Product Enquiry <= 2.6.0 - Unauthenticated Self-Based Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.7.0
- Affected Plugin
- WooCommerce Product Enquiry
- Affected Version
<= 2.6.0- CVSS
- 4.7Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2023-32796
At a glance
CVE-2023-32796 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WooCommerce Product Enquiry WordPress plugin, affecting versions <= 2.6.0. It carries a CVSS score of 4.7 (reachable over the network). Exploitation requires no authentication. The issue is fixed in version 2.7.0; sites on affected versions should update now. Disclosed November 2023, reported by Emili Castells.
Vulnerability Overview
The WooCommerce Product Enquiry plugin for WordPress is vulnerable to Self-Cross-Site Scripting via the enquiry form fields in versions up to, and including, 2.6.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in the page an enquiry form is on, though it would require successful social engineering to get the user to input the malicious payload into form fields.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in WooCommerce Product Enquiry <= 2.6.0 takes no account at all. 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 WooCommerce Product Enquiry the fix is 2.7.0: builds <= 2.6.0 are affected, anything from 2.7.0 onward is not.
Remediation
Update to version 2.7.0, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WooCommerce Product Enquiry 2.7.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C