Auth bypass in Phonepe Payment Solutions

CVE-2026-11575

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.

Vulnerability class: Broken Access Control

Published · last modified .

CVSS v3 metric

CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.

EPSS exploit prediction

EPSS: 0.004 (28.3th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 28th percentile — 28.3% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2026-11575: held from 0.004 to 0.004.

EPSS over last 30 days · oldest: 0.004 · newest: 0.004 · change: 0.000

Affected products

  • Phonepe Payment Solutions — versions 0

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2026-11575?
CVE-2026-11575 is a high-severity vulnerability in Phonepe Payment Solutions, classified under Missing Authorization. CVSS score: 7.5/10. Published 2026-07-17.
How severe is CVE-2026-11575?
High severity. CVSS v3 base score is 7.5 out of 10.