CVE-2026-91075: Eupago Gateway For Woocommerce vulnerability

medium 5.3 plugin closed published 2026-11-03

Affected versions: 4.5.0 to 4.7.5
Fixed in: unknown
Severity: Medium · CVSS 5.3
Active installs: closed
Type: Security issue

What an attacker needs

Access: None. No account or login is needed.

CVSS vector (score by WPScan): CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

What to do now

Replace Eupago Gateway For Woocommerce. A closed plugin gets no updates through WordPress, so this hole stays open.
Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deactivating alone leaves its files on the server.
Not sure which version you run? Check your version against every known Eupago Gateway For Woocommerce issue.
If you ran an affected version and something looks off (new admin users, spam pages, redirects), run the free scan below.

The advisory

The Eupago Gateway For Woocommerce WordPress plugin from 4.5.0 through 4.7.5 does not verify the authenticity of incoming payment-confirmation webhook requests in some configurations, allowing unauthenticated attackers to forge a payment confirmation and mark a pending order as paid without paying for it.

Description from the CVE record, published by WPScan (the CVE Numbering Authority), via the NVD entry for CVE-2026-91075.

References

NVD CVE-2026-91075 nvd.nist.gov
WPScan advisory wpscan.com

Ran an affected version? Check your site for signs of a hack

The free scan reads the public side of your site and looks for spam pages, hidden redirects, injected scripts and blacklist entries. No login, no install, about a minute.

Already hacked? Flat $499 cleanup with a 30-day reinfection guarantee.

Where this data comes from

CVE record, score and references: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Versions and install counts: wordpress.org/plugins/eupago-gateway-for-woocommerce (Plugins API), fetched 2026-11-04.
The summary, “what an attacker needs” and “what to do” sections are our plain-English reading of the record and the plugin's release history; the quoted description is the record's own text. Spot an error? Email Daniel.