dbcve.org
Funnelkit AutomationsWordPress extension · Funnelkit

CVE-2023-50857

HIGH · 7.2 CVSS v3.1 Published 2023-12-28
Fix available
A fix is available. Upgrade to after 2.6.1 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 Recover WooCommerce Cart Abandonment, Newsletter, Email Marketing, Marketing Automation By FunnelKit.This issue affects Recover WooCommerce Cart Abandonment, Newsletter, Email Marketing, Marketing Automation By FunnelKit: from n/a through 2.6.1.

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 · moderate confidence

SQL Injection vulnerability in FunnelKit Recover WooCommerce Cart Abandonment plugin allows attackers to inject malicious SQL commands through unsanitized user inputs due to improper neutralization of special elements in SQL commands. This could allow unauthorized database access, data exfiltration, or manipulation of database records.

MitigationUpdate to the latest version of FunnelKit plugin (post 2.6.1) which should contain the patched code. Until then, disable the plugin or restrict administrative access as a temporary measure. Implement parameterized queries or prepared statements in the codebase to prevent similar issues.

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
Funnelkit AutomationsWordPress extension
Affected:<= 2.6.1

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 plugin is installed
    Navigate to WordPress admin dashboard > Plugins and search for 'FunnelKit' or 'Funnelkit Automations' in the installed plugins list
    Affected if Plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin > Plugins, find FunnelKit Automations and view the version number displayed below the plugin name
    Affected if Version number is 2.6.1 or lower
  3. Confirm cart abandonment feature is active
    Navigate to FunnelKit settings or Cart Abandonment section in WordPress admin to verify the recovery feature is enabled and configured
    Affected if Cart abandonment tracking is enabled and storing customer data
  4. Review access to vulnerable endpoint
    Check if the site has any public-facing exposure to the /wp-json/funnelkit/ endpoint or admin-ajax.php routes used by the plugin
    Affected if Plugin endpoints are accessible without proper authentication checks

Your environment is affected if FunnelKit Automations plugin version 2.6.1 or lower is installed with the cart abandonment feature enabled and accessible.

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.6.1
Interim mitigation

Update to the latest version of FunnelKit plugin (post 2.6.1) which should contain the patched code. Until then, disable the plugin or restrict administrative access as a temporary measure. Implement parameterized queries or prepared statements in the codebase to prevent similar issues.

Recommended fix Moderate confidence

FunnelKit Automations version 2.6.2 or later

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate FunnelKit Automations (formerly FunnelKit Recover WooCommerce Cart Abandonment)
  4. 4. If an update is available, click 'Update Now' to install the latest version that addresses CVE-2023-50857
  5. 5. After updating, verify the plugin version is newer than 2.6.1
  6. 6. Test critical functionality (cart abandonment, email automation) to ensure the update did not break existing workflows
Caveat Review FunnelKit changelog for any breaking changes between 2.6.1 and the latest version before updating in production environments

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

Fix this in Funnelkit Automations Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50857 — 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-50857 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