PhonePe Payment Solutions < 3.1.0 - Unauthenticated Payment Bypass via Forged Callback
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Unknown | PhonePe Payment Solutions | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Phonepe | Phonepe Payment Solutions |
|
||||||||
| Wordpress | Wordpress |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.358% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Phonepe
Phonepe phonepe Payment Solutions Wordpress Wordpress wordpress |
|
| Vendors & Products |
Phonepe
Phonepe phonepe Payment Solutions Wordpress Wordpress wordpress |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-862 | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | PhonePe Payment Solutions < 3.1.0 - Unauthenticated Payment Bypass via Forged Callback | |
| References |
|