CoCart 4.9.0 - 4.9.6 - Cross-Site Request Forgery to Privilege Escalation
Strategic Overview
- Status
- Patched in 4.9.7
- Affected Plugin
- CoCart – Headless REST API for WooCommerce
- Affected Version
4.9.0 – 4.9.6- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2026-93549
At a glance
CVE-2026-93549 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the CoCart WordPress plugin, affecting versions 4.9.0 – 4.9.6. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.9.7; sites on affected versions should update now. Disclosed October 2026, reported by Naoki Kawahigashi.
Vulnerability Overview
The CoCart plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions 4.9.0 through 4.9.6. This is due to its REST API authentication not filtering to its own endpoints, making nonce validation obsolete on all WordPress REST API endpoints. This makes it possible for unauthenticated attackers to call all REST API endpoints, including one to create new administrative users, 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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in CoCart 4.9.0 – 4.9.6 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 CoCart the fix is 4.9.7: builds 4.9.0 – 4.9.6 are affected, anything from 4.9.7 onward is not.
Remediation
Update to version 4.9.7, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to CoCart: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: CoCart 4.9.7 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in CoCart – Headless REST API for WooCommerce
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C