# CVE-2026-94273: Snap Finance <= 3.11.0 - Unauthenticated Payment Confirmation Forgery via snap_finance_complete_payment

> Unauthenticated attackers can forge payment confirmations to mark arbitrary WooCommerce orders as paid without completing payment.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-qrcf-6rx9-2mwc

## What is CVE-2026-94273?

CVE-2026-94273 is a medium-severity vulnerability in Unknown Snap Finance, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Snap Finance WordPress plugin through 3.11.0 does not verify that the payment provider's response actually confirms a completed, approved transaction before marking a WooCommerce order as paid, allowing unauthenticated attackers to mark arbitrary orders as paid without completing payment.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-94273 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94273 is a medium-severity vulnerability in Unknown Snap Finance, published on 19 Oct 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-94273 in the wild and no public exploit code.

Affected product: Unknown Snap Finance. 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-94273/ (Markdown: https://insights.sbomify.com/CVE-2026-94273/index.md)
```

## Sources

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

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