Unauthorized order cancellation via nonce bypass
Published Aug 18, 2026 · Updated Aug 18, 2026
Broken authentication in Flutterwave WooCommerce through 3.3.0 allows remote attackers to cancel orders via crafted payment-verification requests. In flw_verify_payment(), the callback gate uses !isset($_GET['_wpnonce']) && !wp_verify_nonce(...), so any request that merely supplies the _wpnonce parameter bypasses nonce validation; the handler then trusts tx_ref, derives the order ID from it, and calls the cancel path when status=cancelled. Exploitation requires network reachability to the public WooCommerce API endpoint and knowledge of a valid transaction reference for the target order; observed impact is unauthorized order cancellation and related order-state changes rather than full site compromise.
Summary
What happened
Broken authentication in Flutterwave WooCommerce through 3.3.0 allows remote attackers to cancel orders via crafted payment-verification requests. In flw_verify_payment(), the callback gate uses !isset($_GET['_wpnonce']) && !wp_verify_nonce(...), so any request that merely supplies the _wpnonce parameter bypasses nonce validation; the handler then trusts tx_ref, derives the order ID from it, and calls the cancel path when status=cancelled. Exploitation requires network reachability to the public WooCommerce API endpoint and knowledge of a valid transaction reference for the target order; observed impact is unauthorized order cancellation and related order-state changes rather than full site compromise.
The record
- CVE
- CVE-2026-73399
- Published
- Aug 18, 2026
- Updated
- Aug 18, 2026
- Vendor
- Flutterwave
- Product
- Flutterwave WooCommerce
- Classifications
- CWE-288, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 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=n/a <=3.3.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