Unauthenticated payment bypass via forged callback
Published Jul 17, 2026 · Updated Jul 17, 2026
Missing callback authorization in PhonePe Payment Solutions before 3.1.0 allows remote attackers to mark unpaid WooCommerce orders as paid. The REST callback handler validates X-VERIFY with an empty legacy Salt Key, reducing the expected signature to SHA-256 of the attacker-supplied base64 payload. WooCommerce and the gateway must be enabled, and the attacker must know an unpaid order ID and exact total; one forged request changes that order to paid.
Summary
What happened
Missing callback authorization in PhonePe Payment Solutions before 3.1.0 allows remote attackers to mark unpaid WooCommerce orders as paid. The REST callback handler validates X-VERIFY with an empty legacy Salt Key, reducing the expected signature to SHA-256 of the attacker-supplied base64 payload. WooCommerce and the gateway must be enabled, and the attacker must know an unpaid order ID and exact total; one forged request changes that order to paid.
The record
- CVE
- CVE-2026-11575
- Published
- Jul 17, 2026
- Updated
- Jul 17, 2026
- Vendor
- PhonePe
- Product
- PhonePe Payment Solutions
- Classifications
- CWE-862, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 17, 2026CVE publishedPublication date reported by the CVE source.
- Jul 17, 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 <3.1.0
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.
Public exploit references
- WPScan forged payment callback proof of conceptfunctional · validated
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