Razorpay vulnerabilities
Published CVEs affecting Razorpay products: 3 record(s), with severity, exploitation and fixes.
CVE-2026-110222
Medium · 5.3
CWE-918 Oct 13, 2026
Razorpay IFSC Ruby gem through 2.0.62 SSRF via IFSC lookup
Razorpay IFSC Ruby gem through 2.0.62 contains a server-side request forgery vulnerability that allows attackers to redirect API requests by supplying a crafted IFSC code to IFSC.find or IFSC#get. Attackers can submit network-path references or absolute URIs that URI.join resolves as a new host, sending GET requests to internal or attacker-chosen hosts and returning parsed response fields.
CVE-2026-39656
Medium · 5.3
CWE-862 Apr 8, 2026
WordPress Razorpay for WooCommerce plugin <= 4.8.2 - Broken Access Control vulnerability
Missing Authorization vulnerability in Razorpay Razorpay for WooCommerce woo-razorpay allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Razorpay for WooCommerce: from n/a through <= 4.8.2.
CVE-2025-14294
Medium · 5.3
CWE-306 Feb 19, 2026
Razorpay for WooCommerce <= 4.7.8 - Missing Authentication to Unauthenticated Order Modification
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.