CVE-2026-7862
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Eupago Gateway For WooCommerce plugin before version 4.7.2 lacks proper authentication and authorization checks on its refund request handler. This allows unauthenticated attackers to submit refund requests for any WooCommerce order using the merchant's payment gateway credentials. For certain payment methods, attackers can also specify an attacker-controlled bank account as the refund destination, enabling direct theft of funds.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Eupago Gateway For WooCommerce is installedIn WordPress admin, go to Plugins > Installed Plugins and search for 'Eupago Gateway For WooCommerce'. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'eupago' and 'gateway' in the name.Affected if The plugin appears in the WordPress plugin list or filesystem
-
Check the installed version numberIn WordPress admin > Plugins > Installed Plugins, click on the Eupago Gateway For WooCommerce plugin to view its details. Note the version number displayed.Affected if The version displayed is below 4.7.2 (for example, 4.7.1, 4.7.0, or earlier)
-
Confirm WooCommerce is activeIn WordPress admin > Plugins, verify that WooCommerce is installed and activated. The vulnerability only applies when WooCommerce is running.Affected if WooCommerce is activated and the plugin version is below 4.7.2
The environment is affected if the Eupago Gateway For WooCommerce plugin version is below 4.7.2 and WooCommerce is active, as the unauthenticated refund endpoint becomes exploitable.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate the Eupago Gateway For WooCommerce plugin to version 4.7.2 or later immediately. Until patched, consider disabling the plugin or implementing web application firewall rules to block unauthorized access to the refund endpoint.
Version 4.7.2 or later
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the 'Eupago Gateway For Woocommerce' plugin
- 4. Check the current version number
- 5. If the installed version is below 4.7.2, click 'Update Now' to upgrade to version 4.7.2 or latest available version
- 6. After updating, verify the new version number reflects the update
- 7. Test the refund functionality to ensure legitimate operations still work correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7862 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-7862 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data