PhonePe Payment Solutions < 3.1.0 - Unauthenticated Payment Bypass via Forged Callback
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · High · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-862.
Summary
The PhonePe Payment Solutions WordPress plugin before 3.1.0 does not properly verify the authenticity of incoming payment callbacks: the secret used to validate the callback signature is empty on sites configured through the current setup flow, so the expected signature reduces to an unkeyed hash of the request body that anyone can compute. This allows unauthenticated attackers to forge a payment-success notification and mark unpaid WooCommerce orders as paid without any payment being made.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Unknown | PhonePe Payment Solutions | before 3.1.0 | 3.1.0 | Patch available | CNA |
- PhonePe Payment Solutions VendorUnknown Affected before 3.1.0 Fixed in 3.1.0 Patch available CNA
Remediation
- Fix · CNA PhonePe Payment Solutions (Unknown) Fixed in 3.1.0
Timeline
- 2026-10-02 Threatist record created from CVE-2026-11575
- 2026-10-03 Alias added: GHSA-vf96-qpw4-cqjr
References
Sources
- CVE-2026-11575 · CVE Program
- CVE-2026-11575 · NVD
- FIRST EPSS
- GHSA-vf96-qpw4-cqjr · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences