# CVE-2026-103324: Business logic in Cardinity Payment Gateway for WooCommerce

> Unauthenticated attackers can forge payment notifications to mark arbitrary orders as paid or failed due to an empty default signing secret.

- **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:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-gpxw-6pc7-r537

## What is CVE-2026-103324?

CVE-2026-103324 is a medium-severity vulnerability in Unknown Cardinity Payment Gateway for WooCommerce, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Cardinity Payment Gateway for WooCommerce WordPress plugin before 3.4.2 does not properly verify the authenticity of the payment notifications it receives, as the secret used to sign them is empty by default, allowing unauthenticated attackers to forge an approved-payment notification and mark arbitrary orders as paid, or force them to failed.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2026-103324 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103324 is a medium-severity vulnerability in Unknown Cardinity Payment Gateway for WooCommerce, published on 15 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-103324 in the wild and no public exploit code.

Affected product: Unknown Cardinity Payment Gateway 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-103324/ (Markdown: https://insights.sbomify.com/CVE-2026-103324/index.md)
```

## Sources

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

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