# CVE-2026-103329: Super Payments < 1.43.1 - Unauthenticated Payment Confirmation Forgery via Webhook Signature

> Unauthenticated attackers can forge webhook signatures to mark arbitrary WooCommerce orders as paid without actual 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:** 9 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-h768-c99r-wgcc

## What is CVE-2026-103329?

CVE-2026-103329 is a medium-severity authentication bypass vulnerability in Unknown Super Payments, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Super Payments WordPress plugin before 1.43.1 does not properly verify the authenticity of incoming payment webhook notifications, as the signing key used to validate their signature is empty by default, allowing unauthenticated attackers to forge a valid signature and mark arbitrary WooCommerce orders as paid without payment.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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


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

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

## Is CVE-2026-103329 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103329 is a medium-severity authentication bypass vulnerability in Unknown Super Payments, published on 9 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-103329 in the wild and no public exploit code.

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

## Sources

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

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