Payment forgery via unauthenticated notification processing
Published Oct 31, 2026 · Updated Oct 31, 2026
Payment forgery in PAYable Payment Gateway for WooCommerce before 1.3.1 allows remote attackers to alter order status via callbacks. The payment-notification handler trusts incoming notifications without verifying their authenticity before marking an order paid or failed. No authentication is required, and affected orders include those placed using other payment methods.
Summary
What happened
Payment forgery in PAYable Payment Gateway for WooCommerce before 1.3.1 allows remote attackers to alter order status via callbacks. The payment-notification handler trusts incoming notifications without verifying their authenticity before marking an order paid or failed. No authentication is required, and affected orders include those placed using other payment methods.
The record
- CVE
- CVE-2026-94361
- Published
- Oct 31, 2026
- Updated
- Oct 31, 2026
- Vendor
- Payable
- Product
- PAYable Payment Gateway for WooCommerce
- Classifications
- CWE-862, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 31, 2026CVE publishedPublication date reported by the CVE source.
- Oct 31, 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.3.1
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.
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