dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-2186

HIGH · 7.5 CVSS v3.1 Published 2025-03-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
The Recover WooCommerce Cart Abandonment, Newsletter, Email Marketing, Marketing Automation By FunnelKit plugin for WordPress is vulnerable to SQL Injection via the ‘automationId’ parameter in all versions up to, and including, 3.5.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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

The FunnelKit plugin for WordPress is vulnerable to SQL Injection via the 'automationId' parameter in versions up to 3.5.1. The vulnerability stems from insufficient escaping of user-supplied input combined with a lack of prepared statements in the SQL query, allowing unauthenticated attackers to inject arbitrary SQL commands.

MitigationUpdate the FunnelKit plugin to version 3.5.2 or later which contains the fix for this SQL injection vulnerability. If immediate patching is not possible, consider deploying a WAF rule to block SQL injection attempts targeting the automationId parameter.

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

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Check installed FunnelKit version
    In WordPress admin, go to Plugins > Installed Plugins > FunnelKit and note the version number displayed. Alternatively, check the plugin header in wp-content/plugins/funnelkit/funnelkit.php for the 'Version' comment.
    Affected if The version is 3.5.1 or lower, or if you cannot confirm the version is 3.5.2 or later.
  2. Identify FunnelKit automation endpoint exposure
    Check if your site exposes the automation endpoint that accepts the automationId parameter. This typically involves requests to /?automation=1 or similar FunnelKit-related AJAX or front-end routes. Review your web server logs or use a sitemap scanner to identify accessible FunnelKit endpoints.
    Affected if The automation functionality is active and accessible without authentication.
  3. Inspect request handling for automationId parameter
    Examine your HTTP access logs for requests containing 'automationId' as a parameter. Search logs for patterns like 'automationId=' in GET or POST requests to your WordPress site.
    Affected if Requests with the automationId parameter are being logged and the plugin version is not confirmed as 3.5.2 or later.
  4. Review plugin file for prepared statement usage
    If you have file access, examine the FunnelKit plugin file that handles automation queries. Look for files containing 'automationId' in the filename or code. Check if the SQL queries use $wpdb->prepare() or parameterized queries. Common paths include wp-content/plugins/funnelkit/
    Affected if The plugin code does not use prepared statements for queries involving the automationId parameter and the version is below 3.5.2.

You are affected if the FunnelKit plugin version is 3.5.1 or lower and the automation functionality is accessible, since the vulnerability allows unauthenticated SQL injection via the automationId parameter.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the FunnelKit plugin to version 3.5.2 or later which contains the fix for this SQL injection vulnerability. If immediate patching is not possible, consider deploying a WAF rule to block SQL injection attempts targeting the automationId parameter.

Recommended fix Moderate confidence

FunnelKit plugin version 3.5.2 or later

  1. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  2. Locate 'FunnelKit - Recover WooCommerce Cart Abandonment, Newsletter, Email Marketing, Marketing Automation'
  3. Check the current installed version (should be 3.5.1 or below)
  4. Update the plugin to the latest available version (3.5.2 or later)
  5. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload the latest version from the WordPress plugin repository
  6. Verify the update was successful by checking the plugin version after updating

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

Have this fixed 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 help mitigating

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-2025-2186 — 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-2025-2186 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