ECPay Ecommerce for WooCommerce <= 1.1.2411060 - Missing Authorization to Authenticated (Subscriber+) Log Deletion
Strategic Overview
- Status
- Patched in 1.1.2502030
- Affected Plugin
- ECPay Ecommerce for WooCommerce
- Affected Version
<= 1.1.2411060- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-13652
At a glance
CVE-2024-13652 is a medium-severity Missing Authorization vulnerability in the ECPay Ecommerce for WooCommerce WordPress plugin, affecting versions <= 1.1.2411060. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.1.2502030; sites on affected versions should update now. Disclosed January 2025, reported by incognito.
Vulnerability Overview
The ECPay Ecommerce for WooCommerce plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'clear_ecpay_debug_log' AJAX action in all versions up to, and including, 1.1.2411060. This makes it possible for authenticated attackers, with Subscriber-level access and above, to clear the plugin's log files.
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 interaction from a victim user.
CWE-862: Missing Authorization
ECPay Ecommerce for WooCommerce <= 1.1.2411060 carries this weakness at clear_ecpay_debug_log, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For ECPay Ecommerce for WooCommerce the fix is 1.1.2502030: builds <= 1.1.2411060 are affected, anything from 1.1.2502030 onward is not.
Remediation
Update to version 1.1.2502030, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: ECPay Ecommerce for WooCommerce 1.1.2502030 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C