Razorpay for WooCommerce <= 4.5.6 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 4.5.7
- Affected Plugin
- Razorpay for WooCommerce
- Affected Version
<= 4.5.6- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE pending
At a glance
This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Razorpay for WooCommerce WordPress plugin, affecting versions <= 4.5.6. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 4.5.7; sites on affected versions should update now. Disclosed November 2023.
Vulnerability Overview
The Razorpay for WooCommerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.5.6. This is due to missing nonce validation on several functions hooked via admin_post. This makes it possible for unauthenticated attackers to update, direct, create, and reverse transfers through the plugin 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 interaction from a victim user.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Razorpay for WooCommerce <= 4.5.6 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 Razorpay for WooCommerce the fix is 4.5.7: builds <= 4.5.6 are affected, anything from 4.5.7 onward is not.
Remediation
Update to version 4.5.7, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Razorpay for WooCommerce: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Razorpay for WooCommerce 4.5.7 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Razorpay for WooCommerce
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C