Cart All In One For WooCommerce <= 1.1.10 - Cross-Site Request Forgery to Cart Changes
Strategic Overview
- Status
- Patched in 1.1.11
- Affected Plugin
- CartSuite – Cart All In One For WooCommerce
- Affected Version
<= 1.1.10- CVSS
- 5.4Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2022-46806
At a glance
CVE-2022-46806 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the CartSuite WordPress plugin, affecting versions <= 1.1.10. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.1.11; sites on affected versions should update now. Disclosed February 2023, reported by Cat.
Vulnerability Overview
The Cart All In One For WooCommerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.1.10. This is due to missing or incorrect nonce validation on numerous functions in the 'VI_WOO_CART_ALL_IN_ONE_Frontend_Frontend' class. This makes it possible for unauthenticated attackers to get various information (such as menu cart text) and change some cart information (item quantities, adding items, applying coupons, setting display style) via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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-352: Cross-Site Request Forgery (CSRF)
CartSuite <= 1.1.10 carries this weakness at VI_WOO_CART_ALL_IN_ONE_Frontend_Frontend, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For CartSuite the fix is 1.1.11: builds <= 1.1.10 are affected, anything from 1.1.11 onward is not.
Remediation
Update to version 1.1.11, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to CartSuite: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: CartSuite 1.1.11 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in CartSuite – Cart All In One For WooCommerce
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C