Direct Payments for WooCommerce – Bank Transfer, Mobile Money, Crypto and Peer-to-Peer (P2P) Payments < 2.5.3 - Missing Authorization
Strategic Overview
- Status
- Patched in 2.5.3
- Affected Plugin
- Direct Payments for WooCommerce – Bank Transfer, Mobile Money, Crypto and Peer-to-Peer (P2P) Payments
- Affected Version
< 2.5.3- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-12966
At a glance
CVE-2026-12966 is a medium-severity Missing Authorization vulnerability in the Direct Payments for WooCommerce WordPress plugin, affecting versions < 2.5.3. 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.5.3; sites on affected versions should update now. Disclosed August 2026, reported by Pedro Pinho.
Vulnerability Overview
The Direct Payments for WooCommerce – Bank Transfer, Mobile Money, Crypto and Peer-to-Peer (P2P) Payments plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to 2.5.3 (exclusive). This makes it possible for unauthenticated attackers to perform an unauthorized action.
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 Direct Payments for WooCommerce < 2.5.3 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 Direct Payments for WooCommerce the fix is 2.5.3: builds < 2.5.3 are affected, anything from 2.5.3 onward is not.
Remediation
Update to version 2.5.3, 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: Direct Payments for WooCommerce 2.5.3 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