Unauthenticated payment bypass via transaction ID reuse
Published Aug 6, 2026 · Updated Aug 6, 2026
Payment bypass in Integrate PhonePe with WooCommerce 1.2.1 and earlier allows remote attackers to mark arbitrary orders as paid. The payment-completion handler accepts independent client-supplied order and transaction identifiers, verifies only that the transaction succeeded, and marks the selected order paid without authenticating the request or binding that transaction to the order. One valid transaction identifier and a reachable callback are sufficient to reuse a payment across orders, causing goods or services to appear paid without corresponding payment.
Summary
What happened
Payment bypass in Integrate PhonePe with WooCommerce 1.2.1 and earlier allows remote attackers to mark arbitrary orders as paid. The payment-completion handler accepts independent client-supplied order and transaction identifiers, verifies only that the transaction succeeded, and marks the selected order paid without authenticating the request or binding that transaction to the order. One valid transaction identifier and a reachable callback are sufficient to reuse a payment across orders, causing goods or services to appear paid without corresponding payment.
The record
- CVE
- CVE-2026-10599
- Published
- Aug 6, 2026
- Updated
- Aug 6, 2026
- Vendor
- Sarankumar
- Product
- Integrate PhonePe with WooCommerce
- Classifications
- CWE-639, CWE-345, T1565
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 6, 2026CVE publishedPublication date reported by the CVE source.
- Aug 6, 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=0 <=1.2.1
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