Bulgarisation for WooCommerce <= 3.0.14 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 3.0.15
- Affected Plugin
- Bulgarisation for WooCommerce
- Affected Version
<= 3.0.14- CVSS
- 7.3High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-2395
At a glance
CVE-2024-2395 is a high-severity Missing Authorization vulnerability in the Bulgarisation for WooCommerce WordPress plugin, affecting versions <= 3.0.14. It carries a CVSS score of 7.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.0.15; sites on affected versions should update now. Disclosed March 2024, reported by Francesco Carlucci.
Vulnerability Overview
The Bulgarisation for WooCommerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.0.14. This is due to missing or incorrect nonce validation on several functions. This makes it possible for unauthenticated attackers to generate and delete labels 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, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in Bulgarisation for WooCommerce <= 3.0.14 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 Bulgarisation for WooCommerce the fix is 3.0.15: builds <= 3.0.14 are affected, anything from 3.0.15 onward is not.
Remediation
Update to version 3.0.15, 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: Bulgarisation for WooCommerce 3.0.15 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C