# CVE-2026-16947: Server-side request forgery in Total processing card payments for WooCommerce

> Unauthenticated attackers can exploit SSRF to steal payment gateway credentials and forge successful payment responses for arbitrary orders.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 29 Aug 2026
- **Updated:** 30 Aug 2026
- **Also known as:** GHSA-675h-pw44-fcfq

## What is CVE-2026-16947?

CVE-2026-16947 is a critical server-side request forgery vulnerability in Unknown Total processing card payments for WooCommerce, published on 29 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Total processing card payments for WooCommerce WordPress plugin through 7.3 does not validate a user-supplied path before using it to build a server-side verification request, and does not verify the authenticity of the response, allowing unauthenticated attackers to redirect that request to an arbitrary host (disclosing the merchant's payment-gateway credentials) and to forge a success response that marks arbitrary WooCommerce orders as paid.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-16947 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16947 is a critical server-side request forgery vulnerability in Unknown Total processing card payments for WooCommerce, published on 29 Aug 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-16947 in the wild and no public exploit code.

Affected product: Unknown Total processing card payments 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-16947/ (Markdown: https://insights.sbomify.com/CVE-2026-16947/index.md)
```

## Sources

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

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