Unauthenticated order payment bypass via unvalidated status notifications
Published Jun 4, 2024 · Updated Apr 8, 2026
Payment validation bypass in Checkout Cielo for WooCommerce 1.1.0 and earlier allows remote attackers to mark unpaid orders as paid. The update_order_status() function treats an unauthenticated status notification as proof of payment without validating its authenticity. No WordPress account is required, and a forged notification triggers paid-order processing despite the absence of a validated Cielo payment.
Summary
What happened
Payment validation bypass in Checkout Cielo for WooCommerce 1.1.0 and earlier allows remote attackers to mark unpaid orders as paid. The update_order_status() function treats an unauthenticated status notification as proof of payment without validating its authenticity. No WordPress account is required, and a forged notification triggers paid-order processing despite the absence of a validated Cielo payment.
The record
- CVE
- CVE-2024-1718
- Published
- Jun 4, 2024
- Updated
- Apr 8, 2026
- Vendor
- Claudio Sanches
- Product
- Claudio Sanches - Checkout Cielo for WooCommerce
- Classifications
- CWE-345, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 4, 2024CVE publishedPublication date reported by the CVE source.
- Apr 8, 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.1.0
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