PLUGIN SECURITY

Is Razorpay for WooCommerce safe?

Known vulnerabilities, PHP compatibility and safer alternatives for the Razorpay for WooCommerce WordPress plugin — checked against WP Clinic's local security database.

What this plugin does

  • Slug: woo-razorpay

Maintenance status

Known vulnerabilities

6 known CVEs on file for Razorpay for WooCommerce. Reported between 2023 and 2026.

CVE Vulnerability Type Severity Affected Fixed in Published Status
CVE-2026-104639 Razorpay for WooCommerce [woo-razorpay] < 4.8.9 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') Medium 4.1 < 4.8.9 4.8.9 2026-11-06 —
CVE-2026-104338 Razorpay for WooCommerce [woo-razorpay] < 4.8.9 Missing Authorization Low 3.7 < 4.8.9 4.8.9 2026-11-06 —
CVE-2026-104337 Razorpay for WooCommerce [woo-razorpay] < 4.8.9 Exposure of Sensitive Information to an Unauthorized Actor Medium 5.3 < 4.8.9 4.8.9 2026-11-06 —
— Razorpay for WooCommerce [woo-razorpay] < 4.8.8 Authorization Bypass Through User-Controlled Key Medium 5.3 < 4.8.8 4.8.8 2026-08-17 —
CVE-2026-104118 Razorpay for WooCommerce [woo-razorpay] < 4.8.8 Authorization Bypass Through User-Controlled Key Unknown < 4.8.8 4.8.8 2026-08-17 —
CVE-2025-14294 Razorpay for WooCommerce [woo-razorpay] < 4.7.9 Missing Authentication for Critical Function Medium 5.3 < 4.7.9 4.7.9 2026-02-18 —
CVE-2026-39656 Razorpay for WooCommerce [woo-razorpay] < 4.8.4 — Medium 5.3 < 4.8.4 4.8.4 2026-02-16 —
— Razorpay for WooCommerce [woo-razorpay] < 4.5.7 — Unknown < 4.5.7 4.5.7 2023-11-28 —
+ 5 more known vulnerabilities
CVE Vulnerability Type Severity Affected Fixed in Published Status
— Razorpay for WooCommerce [woo-razorpay] < 4.5.7 — Unknown < 4.5.7 4.5.7 2023-11-28 —
— Razorpay for WooCommerce [woo-razorpay] < 4.5.7 — Unknown < 4.5.7 4.5.7 2023-11-28 —
— Razorpay for WooCommerce [woo-razorpay] < 4.5.7 — Unknown < 4.5.7 4.5.7 2023-11-28 —
— Razorpay for WooCommerce [woo-razorpay] < 4.5.7 — Unknown < 4.5.7 4.5.7 — —
— Razorpay for WooCommerce [woo-razorpay] < 4.5.7 — Unknown < 4.5.7 4.5.7 — —

How to fix it

Update this plugin to the latest release from wordpress.org — each CVE above lists the exact release that fixed it ("Fixed in") when one is on file.

This is the plugin's full known vulnerability history, not a scan of any specific installation — run a free scan of your own site to check your exact installed version.

Check your own WordPress site

Run a free passive scan now, or create a free account and install the WP Clinic plugin for a deep scan of your whole hosting account and AI-assisted repair.