Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach store checkout endpoint
-
DeliveryInitiate WooCommerce order via FlxWoo
-
ExploitTrigger unverified payment-confirmation callback
-
ExecutionOrder marked paid without settlement
-
ImpactObtain goods/services without payment
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK
2 techniques across 2 tactics: Defense Evasion, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The store must be running the FlxWoo plugin below 3.1.1 as its WooCommerce payment/order-confirmation integration, with checkout reachable over the network. Exploitation requires no authentication, no privileges, and no user interaction (AV:N/AC:L/PR:N/UI:N) - an attacker only needs to initiate a checkout and invoke the order-completion path that FlxWoo trusts without processor-side verification. The practical limiting factor is deployment scope: only stores that use FlxWoo (not stock WooCommerce or other payment gateways) to mark orders paid are affected, and impact is limited to fraudulent order completion (integrity), not data disclosure or site downtime. |
| Impact | The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, 7.5 High) reflects a network-reachable, low-complexity, unauthenticated integrity-only impact - consistent with the description of anyone completing an order without paying. This is a genuine, easily-abusable business-logic/authentication flaw rather than an inflated high-CVSS issue: a public POC exists and no user interaction or privileges are required. There is no confidentiality or availability impact, so it will not appear as data theft or outage, but it directly enables financial fraud. No EPSS score was supplied in the input, and the vulnerability is not listed in CISA KEV, so widespread automated exploitation is not confirmed; however, the combination of unauthenticated network access, low complexity, and published exploit code means opportunistic abuse against exposed stores should be treated as a near-term priority. No signals conflict: the network vector and unauthenticated rating align with the described attack. |
| Exploit ScenarioDerived | An attacker adds items to the cart on a store running vulnerable FlxWoo, proceeds to checkout, and triggers the order-completion callback without actually completing payment at the processor. Because the plugin does not verify settlement with the payment processor, the order is marked paid and moves to fulfillment, letting the attacker obtain goods or services for free. A public POC lowers the skill required to reproduce this. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 31, 2026
Payment verification bypass in the FlxWoo WordPress plugin before 3.1.1 allows unauthenticated attackers to complete WooCommerce orders without paying, because the plugin marks orders as paid without confirming the checkout session was actually settled with the payment processor. Publicly available exploit code exists, and a vendor patch is released; no active exploitation is confirmed in CISA KEV. The flaw enables fraudulent free acquisition of goods or services from any store running the plugin.
RemediationAI
Vendor-released patch: upgrade the FlxWoo plugin to version 3.1.1 or later, which is available from the vendor and is the primary fix. Review the WPScan advisory (https://wpscan.com/vulnerability/b866258c-b49b-40db-a0ff-6c0921b5c89f/) for details before updating. Until 3.1.1 is deployed, deactivate the FlxWoo plugin to force payment confirmation back to WooCommerce's native/processor-verified flow (trade-off: checkout via FlxWoo is disabled, interrupting sales), or reconcile all recent orders against the payment processor's dashboard to catch orders marked paid without a matching settled transaction and hold fulfillment of unverified orders. Enabling processor-side webhook verification or manual order review for high-value items reduces fraud exposure while patching is scheduled.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
FlxWoo is an integration plugin bridging WooCommerce (the dominant WordPress e-commerce framework) with a payment flow. The root cause is CWE-287 (Improper Authentication): rather than performing a server-to-server verification (a webhook or an authenticated API callback) against the payment processor to confirm a checkout session's payment status, the plugin trusts a client-driven return/callback and transitions the order to a paid state. This is a classic broken payment-confirmation pattern where the order-completion handler accepts the success signal without validating it out-of-band with the processor of record. The CPE 'cpe:2.3:a:unknown:flxwoo' identifies the affected component as the FlxWoo application across all versions up to the fix.
Know when Flxwoo gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Unauthenticated, low-complexity network abuse of the checkout callback (AV:N/AC:L/PR:N/UI:N) yields fraudulent paid orders - integrity-only (I:H), no confidentiality or availability impact.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The FlxWoo WordPress plugin before 3.1.1 does not verify with the payment processor that a checkout session was actually paid before marking the associated order as paid, allowing unauthenticated attackers to complete WooCommerce orders without paying.
Articles & Coverage 1
Executive ViewAI
FlxWoo WordPress plugin versions before 3.1.1 contain a critical payment verification bypass that allows any unauthenticated user to complete WooCommerce orders without payment. Organizations running affected versions face direct revenue loss through fraudulent orders and operational disruption from fulfilling unpaid purchases.
Apply vendor patch: FlxWoo 3.1.1 or later
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-51411
GHSA-j2wf-m8xp-xm7q
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB