Skip to main content
WordPress plugin recordReviewed

CartFlows vulnerability history and what to check on a funnel checkout

CartFlows can replace the WooCommerce checkout page for a whole store, and its records carry more than one product name.

Read their version fields, then check funnels, checkout fields, upsell steps and the roles that edit them.

CartFlows vulnerability history

Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 11 records for CartFlows. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.

Update to at least version 3.3.1

Worked out from data retrieved on .

Every affected range listed in this source for CartFlows ends before version 3.3.1.

A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.

  1. CartFlows - Funnel Builder & Checkout Plugin for WooCommerce <= 3.3.0 - Missing Authorization

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 3.3.0

    Patched versions: 3.3.1

    Update to at least version 3.3.1.

  2. CartFlows - Funnel Builder & Checkout Plugin for WooCommerce <= 3.3.0 - Unauthenticated Arbitrary Shortcode Execution

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.5)
    Affected versions
    • All versions up to and including 3.3.0

    Patched versions: 3.3.1

    Update to at least version 3.3.1.

  3. CartFlows - Funnel Builder & Checkout Plugin for WooCommerce <= 3.2.0 - Authenticated (Contributor+) Remote Code Execution

    Published:
    Last updated:
    Severity:
    High (CVSS 8.8)
    Affected versions
    • All versions up to and including 3.2.0

    Patched versions: 3.2.1

    Update to at least version 3.2.1.

  4. CartFlows <= 2.2.3 - Missing Authorization

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 2.2.3

    Patched versions: 2.2.4

    Update to at least version 2.2.4.

  5. CartFlows - Checkout & Funnel Builder for WooCommerce <= 2.1.19 - Authenticated (Administrator+) PHP Object Injection

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.6)
    Affected versions
    • All versions up to and including 2.1.19

    Patched versions: 2.2.0

    Update to at least version 2.2.0.

Show 6 older records
  1. WooCommerce Checkout & Funnel Builder by CartFlows - Create High Converting Stores For WooCommerce <= 2.0.7 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.4)
    Affected versions
    • All versions up to and including 2.0.7

    Patched versions: 2.0.8

    Update to at least version 2.0.8.

  2. Funnel Builder by CartFlows <= 2.0.1 - Authenticated (Editor+) Stored Cross-Site Scripting via settings

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.5)
    Affected versions
    • All versions up to and including 2.0.1

    Patched versions: 2.0.2

    Update to at least version 2.0.2.

  3. CartFlows <= 1.11.11 - Insecure Direct Object Reference to Arbitrary Post Deletion

    Published:
    Last updated:
    Severity:
    Low (CVSS 2.7)
    Affected versions
    • All versions before 1.11.12

    Patched versions: 1.11.12

    Update to at least version 1.11.12.

  4. Funnel Builder by CartFlows <= 1.6.12 - Authenticated Stored Cross-Site scripting via FB Pixel ID and Google Analytics ID

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.8)
    Affected versions
    • All versions before 1.6.13

    Patched versions: 1.6.13

    Update to at least version 1.6.13.

  5. WooCommerce Checkout & Funnel Builder by CartFlows - Create High Converting Stores For WooCommerce <= 1.5.15 - Cross-Site Request Forgery Bypass

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions before 1.5.16

    Patched versions: 1.5.16

    Update to at least version 1.5.16.

  6. Funnel Builder <= 1.3.0 - Arbitrary Plugin Activation

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.4)
    Affected versions
    • All versions up to and including 1.3.0

    Patched versions: 1.3.1

    Update to at least version 1.3.1.

Check CartFlows on a live site

Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.

Where CartFlows takes input on a WooCommerce store

Weighing a CartFlows vulnerability starts with what the plugin puts on a store.

The vendor's step article lists six step types: Landing Page, Checkout, Upsell, Downsell, Thank You and Opt-in. Its Store Checkout article says that feature, once enabled, replaces the default WooCommerce checkout page across the entire store.

Shoppers type into the checkout form and the Opt-in step, and the vendor's pre-fill article says URL parameters populate the fields of the CartFlows Checkout page too, a feature it says is enabled by default and only works on that page. Staff add step settings, custom JavaScript and CSS, and funnels imported as .json files.

The roles named in CartFlows vulnerabilities on record

Titles in this history include the wording Authenticated (Contributor+), Authenticated (Editor+) and Authenticated (Administrator+).

WordPress lists Contributor among the choices for New User Default Role in Settings > General. Record what that setting holds on the site. Three examples:

  • CVE-2026-96837, whose title ends Authenticated (Contributor+) Remote Code Execution. Affected: all versions up to and including 3.2.0. Patched: 3.2.1.
  • CVE-2024-29813, whose title ends Authenticated (Editor+) Stored Cross-Site Scripting via settings. Affected: all versions up to and including 2.0.1. Patched: 2.0.2.
  • CVE-2021-24330, whose title ends Authenticated Stored Cross-Site scripting via FB Pixel ID and Google Analytics ID. Affected: all versions before 1.6.13. Patched: 1.6.13.

More than one product name and a repeated ending

Every record in this history is filed under the slug cartflows, whatever its title calls the plugin. Openings include Funnel Builder, Funnel Builder by CartFlows, WooCommerce Checkout & Funnel Builder by CartFlows and CartFlows - Checkout & Funnel Builder for WooCommerce.

The titles of CVE-2026-120853 (affected: all versions up to and including 3.3.0; patched: 3.3.1) and CVE-2026-39477 (affected: all versions up to and including 2.2.3; patched: 2.2.4) both end Missing Authorization, so tell records apart by CVE id and version fields.

Match on the fields: the title of CVE-2021-24330 carries 1.6.12, while its affected versions field reads all versions before 1.6.13.

Where each CartFlows check sits in the dashboard

The vendor's editing article gives every step four actions.

View Step opens it on the front end and Settings opens its configuration panel. Edit Step opens it in the page builder or editor to modify its design and content. Leave Edit Step alone, and close panels without pressing Save Settings.

CartFlows, CartFlows Pro and WooCommerce versions

Record the CartFlows, CartFlows Pro and WooCommerce rows on the Plugins screen: WordPress puts each plugin's version number in the Description column. 1 min read

Published funnels and the Store Checkout

For each funnel in the list at CartFlows > Funnels, open the funnel editor. 1 min read

Checkout fields

The vendor's field article reaches the field list through the Checkout step's settings icon, then Checkout Form > Field Editor, with Custom Field Editor enabled. 1 min read

Upsell and downsell steps

The vendor's step article marks Upsell and Downsell steps as Pro features. 1 min read

Who can edit funnels

CartFlows > Settings > User Role Manager gives each role No Access, Limited Access (funnels and steps only, no global settings) or Full Access, which the vendor says includes creating, editing, importing and exporting funnels and steps. 1 min read

Where a CartFlows version check stops

Which roles User Role Manager admits, what the JavaScript fields add to a checkout and whether a Test Mode banner is showing to shoppers are settings, and no version number records them.

Matching the installed CartFlows version to a range in the history tells you a known record applies to the build you run. It does not tell you whether anyone used the flaw. A WordPress security audit gives the checkout its own pass, on a staging copy or with the payment gateway in test mode: it changes prices, quantities and coupon codes in the cart and checkout requests and lists every script that loads on the checkout page.

Frequently asked questions

Each record has its own affected range and patched versions field. Compare the CartFlows version on the Plugins screen with every range, including records whose titles open with Funnel Builder by CartFlows, then with the update guidance at the top of the history. For fixes in later releases, read the entries the changelog on the WordPress.org listing labels Security Fix.

This page shows only the records the source data files under the slug cartflows. Their fields cannot show whether a record also applies to CartFlows Pro. The vendor's install article has CartFlows Pro uploaded as a separate .zip and says the CartFlows Free plugin is required. Give Pro its own inventory line.

The vendor's gateway article says the CartFlows checkout page supports all payment gateways already supported by WooCommerce. Its one-click upsell article says the gateway used during checkout must support the required tokenisation or reference transaction features for those offers to work properly. Where card numbers are held is not something the pages cited here state. Read the gateway plugin's own documentation and records for it.

They are a dated list of reports with version fields, and this page gives no rating of the plugin. The FAQ on the WordPress.org listing asks for a vulnerability to be reported through the vendor's Bug Bounty Program and not disclosed publicly.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.

Data source and licence

The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.

Copyright 2012-2026 Defiant Inc.

Applies to every record listed below.

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

Copyright 1999-2026 The MITRE Corporation

Applies to 10 of the 11 records listed below.

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.