# CVE-2026-103359: PayDunya WooCommerce Payment Gateway 1.1.6 - Unauthenticated Order Payment Completion via Webhook Forgery


- **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
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-563r-v2v8-6c3q

## What is CVE-2026-103359?

CVE-2026-103359 is a medium-severity vulnerability in Unknown PayDunya WooCommerce Payment Gateway, published on 27 Oct 2026. 

### Official description

The PayDunya WooCommerce Payment Gateway WordPress plugin through 1.1.6 does not verify the authenticity of incoming payment notifications and, until the gateway is configured, authenticates them with a value derived from an empty secret that anyone can compute, allowing unauthenticated attackers to mark arbitrary WooCommerce orders as paid and completed.

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

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


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

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

## Is CVE-2026-103359 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103359 is a medium-severity vulnerability in Unknown PayDunya WooCommerce Payment Gateway, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-103359 in the wild and no public exploit code.

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

## Sources

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

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