Woocommerce Blocker Lite <= 2.1.5 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 2.1.6
- Affected Plugin
- Fraud Prevention For WooCommerce and EDD
- Affected Version
<= 2.1.5- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-39159
At a glance
CVE-2023-39159 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Fraud Prevention For WooCommerce and EDD WordPress plugin, affecting versions <= 2.1.5. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.1.6; sites on affected versions should update now. Disclosed July 2023, reported by Kévin Mosbahi (Mika).
Vulnerability Overview
The Woocommerce Blocker Lite plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.1.5. This is due to missing nonce validation on several of the plugin's functions like wcblu_custom_add_update_options(), wcblu_update_general_settings(), and wcblu_update_rules_settings(). This makes it possible for unauthenticated attackers to invoke this function and update the plugin's settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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.
CWE-352: Cross-Site Request Forgery (CSRF)
Fraud Prevention For WooCommerce and EDD <= 2.1.5 carries this weakness at wcblu_custom_add_update_options(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Fraud Prevention For WooCommerce and EDD the fix is 2.1.6: builds <= 2.1.5 are affected, anything from 2.1.6 onward is not.
Remediation
Update to version 2.1.6, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Fraud Prevention For WooCommerce and EDD: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Fraud Prevention For WooCommerce and EDD 2.1.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Fraud Prevention For WooCommerce and EDD
- 7.5CVE-2026-25443: Fraud Prevention… Unauthenticated Arbitrary Content
CVE-2026-25443 - 6.3CVE-2022-4974: Freemius SDK <= 2.4.2 Missing Authorization Checks
CVE-2022-4974 - 6.1CVE-2023-33999: Freemius SDK <= 2.5.9 Reflected Cross-Site Scripting
CVE-2023-33999 - 4.3CVE-2026-24553: Fraud Prevention For Woocommerce Information Exposure
CVE-2026-24553
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C