Unauthenticated order modification via permissive REST callback
Published Feb 19, 2026 · Updated Feb 19, 2026
Missing authentication in Razorpay for WooCommerce 4.7.8 and earlier allows remote attackers to alter WooCommerce order contact data. The getCouponList() REST handler accepts an order ID and writes billing and shipping email and phone values because its checkAuthCredentials() permission callback always returns true. An attacker needs only a known or guessed order ID; the documented effect is limited to modifying those stored contact fields.
Summary
What happened
Missing authentication in Razorpay for WooCommerce 4.7.8 and earlier allows remote attackers to alter WooCommerce order contact data. The getCouponList() REST handler accepts an order ID and writes billing and shipping email and phone values because its checkAuthCredentials() permission callback always returns true. An attacker needs only a known or guessed order ID; the documented effect is limited to modifying those stored contact fields.
The record
- CVE
- CVE-2025-14294
- Published
- Feb 19, 2026
- Updated
- Feb 19, 2026
- Vendor
- Razorpay
- Product
- Razorpay for WooCommerce
- Classifications
- CWE-306, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 19, 2026CVE publishedPublication date reported by the CVE source.
- Feb 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=* <=4.7.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo