# CVE-2026-7862: Eupago Gateway For Woocommerce < 4.7.2 - Unauthenticated Arbitrary Refund Initiation

> Unauthenticated attackers can initiate arbitrary refunds and redirect funds to their own bank accounts via the Eupago Gateway for WooCommerce plugin.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-fppg-vjhw-hp4m

## What is CVE-2026-7862?

CVE-2026-7862 is a high-severity missing authorization vulnerability in Unknown Eupago Gateway For Woocommerce, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Eupago Gateway For Woocommerce WordPress plugin before 4.7.2 does not properly restrict access to its refund request handler, allowing unauthenticated attackers to initiate refunds against any WooCommerce order using the merchant's payment gateway credentials, and for applicable payment methods, to redirect refunded funds to an attacker-controlled bank account.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-7862 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7862 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7862 is a high-severity missing authorization vulnerability in Unknown Eupago Gateway For Woocommerce, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7862 exists.

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

## Sources

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

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