# CVE-2026-103300: Eurobank WooCommerce Payment Gateway <= 2.1.1 - Unauthenticated Order Payment Forgery via Unverified Callback


- **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:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-gmpq-vcj6-g4r2

## What is CVE-2026-103300?

CVE-2026-103300 is a medium-severity vulnerability in Unknown Eurobank WooCommerce Payment Gateway, published on 26 Oct 2026. 

### Official description

The Eurobank WooCommerce Payment Gateway WordPress plugin through 2.1.1 does not verify that a payment-confirmation request genuinely originates from the payment provider, and ships with the secret that would authenticate it empty by default, allowing unauthenticated attackers to mark any pending order as paid, and to force any order into a failed status without any secret at all.

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

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


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

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

## Is CVE-2026-103300 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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