Fraud Prevention For WooCommerce and EDD <= 2.3.3 - Missing Authorization to Unauthenticated Arbitrary Content Deletion
Strategic Overview
- Status
- Patched in 2.3.4
- Affected Plugin
- Fraud Prevention For WooCommerce and EDD
- Affected Version
<= 2.3.3- CVSS
- 7.5High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-25443
At a glance
CVE-2026-25443 is a high-severity Missing Authorization vulnerability in the Fraud Prevention For WooCommerce and EDD WordPress plugin, affecting versions <= 2.3.3. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 2.3.4; sites on affected versions should update now. Disclosed March 2026, reported by Jarno Vos (jarnovos).
Vulnerability Overview
The Fraud Prevention For WooCommerce and EDD plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to, and including, 2.3.3. 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. A successful exploit has high impact on integrity.
CWE-862: Missing Authorization
Reaching this weakness in Fraud Prevention For WooCommerce and EDD <= 2.3.3 takes no account at all. 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 Fraud Prevention For WooCommerce and EDD the fix is 2.3.4: builds <= 2.3.3 are affected, anything from 2.3.4 onward is not.
Remediation
Update to version 2.3.4, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Fraud Prevention For WooCommerce and EDD 2.3.4 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Fraud Prevention For WooCommerce and EDD
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C