# CVE-2024-13652: ECPay Ecommerce for WooCommerce <= 1.1.2411060 - Missing Authorization to Authenticated (Subscriber+) Log Deletion

> Authenticated subscribers can delete plugin debug logs due to missing capability checks in the ECPay Ecommerce for WooCommerce plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jan 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-2h8h-53wp-5m9q

## What is CVE-2024-13652?

CVE-2024-13652 is a medium-severity missing authorization vulnerability in ecpaytechsupport ECPay Ecommerce for WooCommerce, published on 30 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2024-13652?

It affects 1 product.


Products: Ecpay Ecpay Ecommerce for Woocommerce.

## How do I fix CVE-2024-13652?

No fix has been published for CVE-2024-13652 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-13652 being exploited?

There is no known exploitation of CVE-2024-13652 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-13652 and fix it if it is affected.

What it is: CVE-2024-13652 is a medium-severity missing authorization vulnerability in ecpaytechsupport ECPay Ecommerce for WooCommerce, published on 30 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-13652 in the wild and no public exploit code.

Affected product: ecpaytechsupport ECPay Ecommerce for WooCommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-13652/ (Markdown: https://insights.sbomify.com/CVE-2024-13652/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-13652
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-13652
- OSV: https://osv.dev/vulnerability/CVE-2024-13652

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-13652/
Summaries are generated and may contain mistakes; the official description above is the record.