# CVE-2026-11575: PhonePe Payment Solutions < 3.1.0 - Unauthenticated Payment Bypass via Forged Callback

> Unauthenticated attackers can forge payment callbacks to mark unpaid orders as paid due to missing signature verification in the PhonePe WordPress plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-vf96-qpw4-cqjr

## What is CVE-2026-11575?

CVE-2026-11575 is a high-severity missing authorization vulnerability in Unknown PhonePe Payment Solutions, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-11575?


## How do I fix CVE-2026-11575?

No fix has been published for CVE-2026-11575 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-11575 being exploited?

There is no known exploitation of CVE-2026-11575 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-11575 and fix it if it is affected.

What it is: CVE-2026-11575 is a high-severity missing authorization vulnerability in Unknown PhonePe Payment Solutions, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-11575 in the wild and no public exploit code.

Affected product: Unknown PhonePe Payment Solutions. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-11575/ (Markdown: https://insights.sbomify.com/CVE-2026-11575/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-11575
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-11575
- OSV: https://osv.dev/vulnerability/CVE-2026-11575

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-11575/
Summaries are generated and may contain mistakes; the official description above is the record.