Unauthenticated payment bypass via unchecked checkout success
Published Jul 31, 2026 · Updated Jul 31, 2026
Authentication bypass in FlexPlat FlxWoo before 3.1.1 allows remote attackers to complete WooCommerce orders without payment. The unauthenticated /checkout/success handler changes a pending order to processing after checking only locally stored order metadata, without asking Stripe whether the session was paid. WooCommerce and a configured Stripe secret key are required; successful exploitation triggers paid-order fulfillment without a cleared payment.
Summary
What happened
Authentication bypass in FlexPlat FlxWoo before 3.1.1 allows remote attackers to complete WooCommerce orders without payment. The unauthenticated /checkout/success handler changes a pending order to processing after checking only locally stored order metadata, without asking Stripe whether the session was paid. WooCommerce and a configured Stripe secret key are required; successful exploitation triggers paid-order fulfillment without a cleared payment.
The record
- CVE
- CVE-2026-14830
- Published
- Jul 31, 2026
- Updated
- Jul 31, 2026
- Vendor
- FlexPlat
- Product
- FlxWoo
- Classifications
- CWE-287, T1657
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 31, 2026CVE publishedPublication date reported by the CVE source.
- Jul 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 <3.1.1
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.
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