Order payment forgery via unsigned confirmation callbacks
Published Sep 4, 2026 · Updated Sep 4, 2026
Authentication bypass in ePayco plugin for WooCommerce before 8.4.7 allows remote attackers to mark WooCommerce orders as paid. The public payment callback accepts attacker-controlled transaction fields and updates the referenced order without first validating x_signature against the locally computed gateway signature. No WordPress account or shopper interaction is required; a forged confirmation can falsely record an unpaid order as paid.
Summary
What happened
Authentication bypass in ePayco plugin for WooCommerce before 8.4.7 allows remote attackers to mark WooCommerce orders as paid. The public payment callback accepts attacker-controlled transaction fields and updates the referenced order without first validating x_signature against the locally computed gateway signature. No WordPress account or shopper interaction is required; a forged confirmation can falsely record an unpaid order as paid.
The record
- CVE
- CVE-2026-84043
- Published
- Sep 4, 2026
- Updated
- Sep 4, 2026
- Vendor
- ePayco
- Product
- ePayco plugin for WooCommerce
- Classifications
- CWE-345, T1565.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 4, 2026CVE publishedPublication date reported by the CVE source.
- Sep 4, 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=0 <8.4.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo