PhonePe Payment Solutions: A security weakness
PhonePe Payment Solutions is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is < 3.1.0.
- Component
- PhonePe Payment Solutions
- Plugin slug
phonepe-payment-solutions- Affected
- < 3.1.0
- Safe version
3.1.0- Published
- Jul 17, 2026
- Weakness
- CWE-862 — Missing Authorization
This CVE was published Jul 17, 2026 and is one of 2 known issues for this plugin.
Update, patch or deactivate.
Update PhonePe Payment Solutions to 3.1.0 or later, or disable and remove it until a fixed version is available.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
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.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N