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