dbcve.org
Funnel BuilderWordPress extension · Funnelkit

CVE-2023-50856

HIGH · 7.2 CVSS v3.1 Published 2023-12-28
Fix available
A fix is available. Upgrade to after 2.14.3 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in FunnelKit Funnel Builder for WordPress by FunnelKit – Customize WooCommerce Checkout Pages, Create Sales Funnels & Maximize Profits.This issue affects Funnel Builder for WordPress by FunnelKit – Customize WooCommerce Checkout Pages, Create Sales Funnels & Maximize Profits: from n/a through 2.14.3.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in FunnelKit Funnel Builder for WordPress allows attackers to inject malicious SQL commands through unsanitized input. The flaw exists in versions up to 2.14.3 due to improper neutralization of special elements in SQL queries.

MitigationUpdate FunnelKit Funnel Builder to the latest patched version immediately. If no update is available, disable the plugin until a fix is released. Audit user-supplied input handling in the plugin for proper use of prepared statements.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Funnel BuilderWordPress extension
Affected:<= 2.14.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify FunnelKit Funnel Builder is installed
    Log into WordPress admin, go to Plugins > Installed Plugins, and search for 'FunnelKit Funnel Builder' or 'Funnelkit'. Alternatively, check the /wp-content/plugins/ directory for a folder named 'funnelkit' or similar.
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed version number
    In WordPress admin, go to Plugins > Installed Plugins, find FunnelKit Funnel Builder, and note the version number displayed below the plugin name. Or open the main plugin PHP file (usually funnels.php or class-funnel.php) in /wp-content/plugins/funnelkit/ and look for a 'Version' header in the file comments.
    Affected if The version displayed is 2.14.3 or lower, or the version cannot be determined but the plugin is present
  3. Confirm the vulnerability scope
    Compare your installed version against the affected range: any version from the plugin's initial release up to and including 2.14.3 is vulnerable.
    Affected if Your installed version is 2.14.3 or any earlier version, and the plugin is active on the site

You are affected if FunnelKit Funnel Builder plugin is installed and active with a version of 2.14.3 or lower.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.14.3
Interim mitigation

Update FunnelKit Funnel Builder to the latest patched version immediately. If no update is available, disable the plugin until a fix is released. Audit user-supplied input handling in the plugin for proper use of prepared statements.

Recommended fix Moderate confidence

Version 2.14.4 or later (check WordPress plugin repository for latest stable release)

  1. 1. Back up your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate FunnelKit Funnel Builder (also called Funnel Builder or FunnelKit).
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. After updating, verify the plugin is functioning correctly by testing your funnels and checkout flows.
  6. 6. Confirm the updated version is newer than 2.14.3 (the fixed version should be 2.14.4 or higher).

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Funnel Builder Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50856 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-50856 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data