CVE-2026-2838
Stored XSS in WooCommerce Whole Enquiry Cart Plugin
Publication date: 2026-04-08
Last updated on: 2026-04-08
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| woothemes | whole_enquiry_cart | to 1.2.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The Whole Enquiry Cart for WooCommerce plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in the ‘woowhole_success_msg’ parameter. This vulnerability exists in all versions up to and including 1.2.1 due to insufficient input sanitization and output escaping.
Authenticated attackers with administrator-level access can exploit this vulnerability to inject arbitrary web scripts into pages. These scripts will execute whenever a user accesses the injected page.
This vulnerability only affects multi-site WordPress installations and installations where the unfiltered_html setting has been disabled.
How can this vulnerability impact me? :
This vulnerability allows an attacker with administrator privileges to inject malicious scripts that execute in the context of users visiting the affected pages.
Such script execution can lead to unauthorized actions, data theft, or session hijacking for users accessing the injected pages.
Because the vulnerability requires administrator-level access and affects multi-site or restricted HTML installations, the risk is somewhat limited but still significant in those environments.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should update the Whole Enquiry Cart for WooCommerce plugin to a version later than 1.2.1 where the issue is fixed.
Additionally, ensure that your WordPress installation is not a multi-site setup or that unfiltered_html is not disabled, as the vulnerability only affects multi-site installations or those with unfiltered_html disabled.
Limit administrator-level access to trusted users only, since exploitation requires authenticated administrator privileges.