CVE-2025-14294

Razorpay for WooCommerce <= 4.7.8 - Missing Authentication to Unauthenticated Order Modification

2026-02-18 00:00
Marcin Dudek (dudekmar)

Strategic Overview

Status
Patched in 4.7.9
Affected Version
<= 4.7.8
CVSS
5.3Medium
Weakness type
CWE-306 · Missing Authentication for Critical Function
CVE
CVE-2025-14294
View all Razorpay for WooCommerce vulnerabilities

At a glance

CVE-2025-14294 is a medium-severity Missing Authentication for Critical Function vulnerability in the Razorpay for WooCommerce WordPress plugin, affecting versions <= 4.7.8. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.7.9; sites on affected versions should update now. Disclosed February 2026, reported by Marcin Dudek (dudekmar).

Vulnerability Overview

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.

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, and no interaction from a victim user.

CWE-306: Missing Authentication for Critical Function

The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

Remediation

Update to version 4.7.9, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Razorpay for WooCommerce 4.7.9 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C