# CVE-2026-94295: Chikkili Google Pay for WooCommerce <= 1.0.6 - Unauthenticated Payment Confirmation Forgery via Unverified Signature


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-wxfh-552r-23f6

## What is CVE-2026-94295?

CVE-2026-94295 is a medium-severity vulnerability in Unknown Chikkili- Google Pay India for Woocommerce, published on 25 Oct 2026. 

### Official description

The Chikkili- Google Pay India for Woocommerce WordPress plugin through 1.0.6 does not verify that a payment notification actually originated from the payment provider before marking the associated order as paid, allowing unauthenticated attackers to mark arbitrary orders as paid without any payment being made.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-94295 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94295 is a medium-severity vulnerability in Unknown Chikkili- Google Pay India for Woocommerce, published on 25 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-94295 in the wild and no public exploit code.

Affected product: Unknown Chikkili- Google Pay India for Woocommerce. 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-94295/ (Markdown: https://insights.sbomify.com/CVE-2026-94295/index.md)
```

## Sources

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

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