Eupago Gateway For Woocommerce <= 4.7.1 - Missing Authorization to Unauthenticated Arbitrary Refund Initiation
Strategic Overview
- Status
- Patched in 4.7.2
- Affected Plugin
- Eupago Gateway For Woocommerce
- Affected Version
<= 4.7.1- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-7862
At a glance
CVE-2026-7862 is a medium-severity Missing Authorization vulnerability in the Eupago Gateway For Woocommerce WordPress plugin, affecting versions <= 4.7.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.7.2; sites on affected versions should update now. Disclosed May 2026, reported by Pedro Pinho.
Vulnerability Overview
The Eupago Gateway For Woocommerce plugin for WordPress is vulnerable to unauthorized access in versions up to, and including, 4.7.1. This is due to missing nonce verification and capability check on the wp_ajax_nopriv_refund AJAX action in the refund_func function. This makes it possible for unauthenticated attackers to initiate arbitrary refunds on any order without authentication.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in Eupago Gateway For Woocommerce <= 4.7.1 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Eupago Gateway For Woocommerce the fix is 4.7.2: builds <= 4.7.1 are affected, anything from 4.7.2 onward is not.
Remediation
Update to version 4.7.2, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Eupago Gateway For Woocommerce 4.7.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Eupago Gateway For Woocommerce
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C