Skip to main content

FlxWoo CVE-2026-14830

| EUVDEUVD-2026-51411 HIGH
Improper Authentication (CWE-287)
2026-07-31 WPScan GHSA-j2wf-m8xp-xm7q
7.5
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach store checkout endpoint
  2. Delivery
    Initiate WooCommerce order via FlxWoo
  3. Exploit
    Trigger unverified payment-confirmation callback
  4. Execution
    Order marked paid without settlement
  5. Impact
    Obtain 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.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

FlxWoo 0 <3.1.1

Affected Packages

euvd flxwoo fix: 3.1.1

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

Vendor (WPScan) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
vuln.today AI 7.5 HIGH

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.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Lifecycle Timeline

4
CVSS changed
Jul 31, 2026 - 14:22 NVD
7.5 (HIGH)
Patch available
Jul 31, 2026 - 07:01 EUVD
CVE Published
Jul 31, 2026 - 06:00 cve.org
HIGH 7.5
CVE Published
Jul 31, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.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.

Executive ViewAI

Why It Matters

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.

Business Impact: High
Compensating Controls

Apply vendor patch: FlxWoo 3.1.1 or later

Threat Intelligence Overview

EPSS Score
0.1%
Top 96% exploitable
Prevalence
Low
niche WooCommerce payment-integration plugin, limited store footprint
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

58
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy