CVE-2026-11575 PhonePe CVE debrief

Who should care

Users of the PhonePe Payment Solutions WordPress plugin, especially those who have not updated to version 3.1.0 or later, should be aware of this vulnerability and take necessary precautions. This includes reviewing the plugin's configuration, verifying the authenticity of incoming payment callbacks, and monitoring for suspicious payment notifications.

Technical 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. As a result, 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.

Defensive priority

High

Recommended defensive actions

• Update the PhonePe Payment Solutions WordPress plugin to version 3.1.0 or later
• Verify the authenticity of incoming payment callbacks
• Monitor for suspicious payment notifications
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record was published on 2026-07-17T07:16:37.753Z and has not been modified since then. The NVD entry is currently Received. There is limited evidence available about the vulnerability, and defenders should verify the authenticity of incoming payment callbacks. 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.

Official resources