Welcart e-Commerce <= 2.9.4 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 2.9.5
- Affected Plugin
- Welcart e-Commerce
- Affected Version
<= 2.9.4- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE pending
At a glance
This record tracks a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Welcart e-Commerce WordPress plugin, affecting versions <= 2.9.4. 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 2.9.5; sites on affected versions should update now. Disclosed November 2023.
Vulnerability Overview
The Welcart e-Commerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.9.4. This is due to missing or incorrect nonce validation on several functions. This makes it possible for unauthenticated attackers to upload files via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. Since uploaded files were not verified properly, this could lead to arbitrary file upload.
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 Welcart e-Commerce <= 2.9.4 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 Welcart e-Commerce the fix is 2.9.5: builds <= 2.9.4 are affected, anything from 2.9.5 onward is not.
Remediation
Update to version 2.9.5, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Welcart e-Commerce: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Welcart e-Commerce 2.9.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Welcart e-Commerce
- 9.8CVE-2023-5952: Welcart e-Commerce <= 2.9.4 PHP Object Injection
CVE-2023-5952 - 9.8CVE-2016-4828: Welcart e-Commerce <= 1.8.2 Authentication Bypass
CVE-2016-4828 - 9.8CVE-2014-10017: Welcart e-Commerce <= 2.9.1 SQL Injection
CVE-2014-10017 - 8.8CVE-2026-19887: Welcart e-Commerce <= 2.12.1 Arbitrary File Deletion
CVE-2026-19887 - 8.8CVE-2023-5953: Welcart e-Commerce <= 2.9.4 Arbitrary File Upload
CVE-2023-5953 - 8.8CVE-2023-40219: Welcart e-Commerce <= 2.8.21 Arbitrary File Upload
CVE-2023-40219 - 8.8CVE-2023-43493: Welcart e-Commerce <= 2.8.21 SQL Injection
CVE-2023-43493 - 8.8CVE-2023-43610: Welcart e-Commerce <= 2.8.21 SQL Injection
CVE-2023-43610
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C