Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-11575 – Payment Callback Bypass – PhonePe Payment Solutions WordPress Plugin before 3.1.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-11575 is a high-severity payment authorization bypass vulnerability in the PhonePe Payment Solutions WordPress plugin, affecting all versions prior to 3.1.0. The flaw allows unauthenticated remote attackers to forge payment-success callbacks and mark unpaid WooCommerce orders as paid without any actual transaction taking place. The vulnerability carries a CVSS v3.1 score of 7.5 (High) and was remediated in version 3.1.0, released June 25, 2026.

Technical details

  • Root cause: The HMAC signing secret used to validate incoming payment callback signatures is empty on sites configured through the plugin’s current setup flow. This reduces the expected HMAC signature to an unkeyed hash of the request body — a value any attacker can independently compute without possessing any secret material. The plugin also decoded the payload before performing signature verification, meaning untrusted data was processed prior to any authentication check.
  • Trigger conditions: No authentication, credentials, or victim interaction is required. The flaw affects sites configured through the standard plugin setup flow, with no special or non-default configuration needed to be vulnerable.
  • Attack vector: Fully remote and unauthenticated. An attacker sends a crafted HTTP payment-success callback to the plugin’s WooCommerce endpoint, including a forged but computationally valid signature derived from the empty secret.
  • Impact: The attacker can mark arbitrary unpaid WooCommerce orders as fulfilled, enabling fraudulent order completion without any financial transaction occurring. The CVSS impact is limited to Integrity (I:H); there is no confidentiality or availability impact. The practical consequence for affected merchants is financial loss through goods or services delivered without payment.

Affected software

  • PhonePe Payment Solutions WordPress plugin, all versions prior to 3.1.0

Severity

CVSS v3.1 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

Mitigation and recommended actions

  • Immediate action: Update to PhonePe Payment Solutions version 3.1.0 or later. The plugin changelog confirms that version 3.1.0 fixes this vulnerability by authenticating requests before processing payload data and correctly enforcing HMAC signature verification prior to any data decoding.
  • If immediate patching is not feasible: Restrict access to the WooCommerce payment callback endpoint at the web server or WAF level, limiting inbound requests to known PhonePe gateway IP ranges only. This is a temporary control and does not replace patching.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge