Unauthenticated payment forgery via unverified callbacks
Published Oct 14, 2026 · Updated Oct 14, 2026
Payment forgery in Paymentfor Gateway for WooCommerce before 1.0.6 allows remote attackers to mark orders paid via forged notifications. Payment return and notification handlers change order status without authenticating the notification or verifying payment completion. Exploitation requires a reachable affected handler in an active WooCommerce deployment and falsifies payment status without completing payment.
Summary
What happened
Payment forgery in Paymentfor Gateway for WooCommerce before 1.0.6 allows remote attackers to mark orders paid via forged notifications. Payment return and notification handlers change order status without authenticating the notification or verifying payment completion. Exploitation requires a reachable affected handler in an active WooCommerce deployment and falsifies payment status without completing payment.
The record
- CVE
- CVE-2026-94360
- Published
- Oct 14, 2026
- Updated
- Oct 14, 2026
- Vendor
- Welcart Inc.
- Product
- Paymentfor Gateway for WooCommerce
- Classifications
- T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 14, 2026CVE publishedPublication date reported by the CVE source.
- Oct 14, 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 <1.0.6
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.
Get started