Web3 Cryptocurrency Payments by DePay for WooCommerce <= 2.12.17 - Missing Authorization to Information Exposure
Strategic Overview
- Status
- Patched in 2.12.18
- Affected Plugin
- Web3 Crypto Payments by DePay for WooCommerce
- Affected Version
<= 2.12.17- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-12265
At a glance
CVE-2024-12265 is a medium-severity Missing Authorization vulnerability in the Web3 Crypto Payments by DePay for WooCommerce WordPress plugin, affecting versions <= 2.12.17. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.12.18; sites on affected versions should update now. Disclosed December 2024, reported by Tieu Pham Trong Nhan.
Vulnerability Overview
The Web3 Crypto Payments by DePay for WooCommerce plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the /wp-json/depay/wc/debug REST API endpoint in all versions up to, and including, 2.12.17. This makes it possible for unauthenticated attackers to retrieve debug infromation.
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, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in Web3 Crypto Payments by DePay for WooCommerce <= 2.12.17 takes a caller who can reach the endpoint. 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 Web3 Crypto Payments by DePay for WooCommerce the fix is 2.12.18: builds <= 2.12.17 are affected, anything from 2.12.18 onward is not.
Remediation
Update to version 2.12.18, 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: Web3 Crypto Payments by DePay for WooCommerce 2.12.18 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