Payment bypass via unverified confirmation webhooks
Published Nov 3, 2026 · Updated Nov 3, 2026
Payment bypass in Eupago Gateway for WooCommerce allows remote attackers to mark unpaid orders as paid via forged webhooks. In 4.5.0 through 4.7.5, the payment-confirmation handler accepts incoming notifications without verifying their authenticity in some configurations. The supplied record does not identify those configurations; exploitation requires a pending order but no authenticated account.
Summary
What happened
Payment bypass in Eupago Gateway for WooCommerce allows remote attackers to mark unpaid orders as paid via forged webhooks. In 4.5.0 through 4.7.5, the payment-confirmation handler accepts incoming notifications without verifying their authenticity in some configurations. The supplied record does not identify those configurations; exploitation requires a pending order but no authenticated account.
The record
- CVE
- CVE-2026-91075
- Published
- Nov 3, 2026
- Updated
- Nov 3, 2026
- Vendor
- Eupago
- Product
- Eupago Gateway for WooCommerce
- Classifications
- T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 3, 2026CVE publishedPublication date reported by the CVE source.
- Nov 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.5.0 <=4.7.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us