HomeWordPress vulnerabilitiesRazorpay for WooCommerce
Razorpay for WooCommerce vulnerabilities
Razorpay for WooCommerce has 5 known vulnerabilities in this database. The most recent published record is dated 8 Nov 2026.
- Known vulnerabilities
- 5
- Active installs
- 100,000+
- Latest version
- 4.8.9
- Last updated
- 4 Nov 2026
- Most recent
- 8 Nov 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| SQL injection CVE-2026-104639 | Medium 4.1 | Before 4.8.9 | Fixed in 4.8.9 | 8 Nov 2026 |
| Sensitive data exposure CVE-2026-104337 | Medium 5.3 | Before 4.8.9 | Fixed in 4.8.9 | 8 Nov 2026 |
| Broken access control CVE-2026-104338 | Low 3.7 | Before 4.8.9 | Fixed in 4.8.9 | 8 Nov 2026 |
| Broken access control CVE-2026-104118 | Medium 5.3 | Before 4.8.8 | Fixed in 4.8.8 | 4 Oct 2026 |
| Broken access control CVE-2025-14294 | Medium 5.3 | Up to 4.7.8 | Fixed in a later version (latest 4.8.9) | 19 Feb 2026 |
Read the published descriptions
- CVE-2026-104639, 8 Nov 2026
- The Razorpay for WooCommerce WordPress plugin before 4.8.9 does not sanitize and escape a value derived from an incoming webhook request before using it in a SQL query, allowing users able to obtain the webhook secret (administrators) to perform SQL injection attacks. CVE record
- CVE-2026-104337, 8 Nov 2026
- The Razorpay for WooCommerce WordPress plugin before 4.8.9 does not verify ownership of an order before returning a coupon discount computed against that order, allowing unauthenticated attackers to disclose the monetary value of arbitrary customer orders by enumerating order IDs. CVE record
- CVE-2026-104338, 8 Nov 2026
- The Razorpay for WooCommerce WordPress plugin before 4.8.9 does not perform an authorization check on one of its REST routes and derives the acting user's identity from an unauthenticated request parameter, allowing an unauthenticated attacker to cause the request to execute as an arbitrary user account for the duration of the request. Exploitation additionally requires a specific coupon Razorpay for WooCommerce WordPress plugin before 4.8.9 to be active on the site. CVE record
- CVE-2026-104118, 4 Oct 2026
- The Razorpay for WooCommerce WordPress plugin before 4.8.8 does not perform ownership or authorization checks on a REST API route used during checkout, allowing unauthenticated attackers to modify the shipping information stored on arbitrary orders. CVE record
- CVE-2025-14294, 19 Feb 2026
- The Razorpay for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the getCouponList() function in all versions up to, and including, 4.7.8. This is due to the checkAuthCredentials() permission callback always returning true, providing no actual authentication. This makes it possible for unauthenticated attackers to modify the billing and shipping contact information (email and phone) of any WooCommerce order by knowing or guessing the order ID. CVE record
What to do if you run Razorpay for WooCommerce
If you run Razorpay for WooCommerce, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Razorpay for WooCommerce vulnerabilities
Free. We email you when a new vulnerability is published for Razorpay for WooCommerce, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.