Gestpay for WooCommerce <= 20221130 - Cross-Site Request Forgery (CSRF) via ajax_delete_card
Strategic Overview
- Status
- Patched in 20240307
- Affected Plugin
- Ecommerce Fabrick
- Affected Version
<= 20221130- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-0432
At a glance
CVE-2024-0432 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Ecommerce Fabrick WordPress plugin, affecting versions <= 20221130. 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 20240307; sites on affected versions should update now. Disclosed February 2024, reported by Francesco Carlucci.
Vulnerability Overview
The Gestpay for WooCommerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 20221130. This is due to missing or incorrect nonce validation on the 'ajax_delete_card' function. This makes it possible for unauthenticated attackers to delete the default card token for a user 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)
Ecommerce Fabrick <= 20221130 carries this weakness at ajax_delete_card, 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 Ecommerce Fabrick the fix is 20240307: builds <= 20221130 are affected, anything from 20240307 onward is not.
Remediation
Update to version 20240307, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Ecommerce Fabrick: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Ecommerce Fabrick 20240307 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C