# CVE-2026-103325: TiendaCrypto para WooCommerce 1.0.1 - 1.2.1 - Unauthenticated Order Payment Forgery via Webhook HMAC Bypass


- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-g7qx-5gmm-r2gh

## What is CVE-2026-103325?

CVE-2026-103325 is a low-severity vulnerability in Unknown TiendaCrypto para WooCommerce, published on 27 Oct 2026. 

### Official description

The TiendaCrypto para WooCommerce WordPress plugin through 1.2.1 does not correctly verify the authenticity of its payment webhook, validating the request signature against a key that is always empty, which allows unauthenticated attackers to forge webhook notifications and mark arbitrary WooCommerce orders as paid on web servers that preserve request header case.

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

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


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

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

## Is CVE-2026-103325 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103325 is a low-severity vulnerability in Unknown TiendaCrypto para WooCommerce, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-103325 in the wild and no public exploit code.

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

## Sources

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

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