Skip to main content

FlxWoo EUVDEUVD-2026-51411

| CVE-2026-14830 HIGH
Improper Authentication (CWE-287)
2026-07-31 WPScan GHSA-j2wf-m8xp-xm7q
7.5
CVSS 3.1 · Vendor: WPScan
Share

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Lifecycle Timeline

5
Analysis Generated
Jul 31, 2026 - 14:24 vuln.today
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.

AnalysisAI

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

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Reach store checkout endpoint
Delivery
Initiate WooCommerce order via FlxWoo
Exploit
Trigger unverified payment-confirmation callback
Execution
Order marked paid without settlement
Impact
Obtain goods/services without payment

Vulnerability AssessmentAI

Exploitation 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. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment 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. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario 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. …
Remediation 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. … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours: Audit all WordPress instances to identify those running FlxWoo versions before 3.1.1 and assess current order volumes. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

EUVD-2026-51411 vulnerability details – vuln.today

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