CVE-2025-14294 json
Razorpay for WooCommerce <= 4.7.8 - Missing Authentication to Unauthenticated Order Modification
published 2026-02-19 8 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-207873
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 8 mo ago
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected products
- razorpay Razorpay for WooCommerce
Classification
- Weakness
-
- CWE-306 Missing Authentication for Critical Functionality
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/163d42df-148f-431c-891e-dbdc09bf2ae1?source=cve
- plugins.trac.wordpress.org /browser/woo-razorpay/trunk/includes/api/auth.php#L7
- plugins.trac.wordpress.org /browser/woo-razorpay/trunk/includes/api/api.php#L33
- plugins.trac.wordpress.org /browser/woo-razorpay/trunk/includes/api/coupon-get.php#L58
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3436262%40woo-razorpay&new=3436262%40woo-razorpay&sfp_email=&sf
Sources
- CVE List CVE-2025-14294
- NVD CVE-2025-14294
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.