Unauthenticated payment bypass via unchecked webhook
Published Oct 14, 2026 · Updated Oct 14, 2026
Webhook authentication bypass in Asaas Gateway for WooCommerce before 2.7.8 allows remote attackers to mark arbitrary orders as paid. The payment webhook accepts an empty access token in its default configuration and does not verify that the confirmed payment belongs to the order being marked paid. Exploitation requires access to the store's webhook; the reported consequence is falsified order payment status, not execution of server code.
Summary
What happened
Webhook authentication bypass in Asaas Gateway for WooCommerce before 2.7.8 allows remote attackers to mark arbitrary orders as paid. The payment webhook accepts an empty access token in its default configuration and does not verify that the confirmed payment belongs to the order being marked paid. Exploitation requires access to the store's webhook; the reported consequence is falsified order payment status, not execution of server code.
The record
- CVE
- CVE-2026-87974
- Published
- Oct 14, 2026
- Updated
- Oct 14, 2026
- Vendor
- Asaas
- Product
- Asaas 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 <2.7.8
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