dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-14169

HIGH · 7.5 CVSS v3.1 Published 2025-12-12
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 FunnelKit - Funnel Builder for WooCommerce Checkout plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'opid' parameter in all versions up to, and including, 3.13.1.5 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 WordPress plugin fails to properly sanitize the 'opid' parameter before using it in a SQL query, allowing unauthenticated attackers to inject arbitrary SQL commands. The vulnerability is a time-based blind SQL injection, meaning attackers infer information from delayed responses rather than direct output. All versions up to 3.13.1.5 are affected.

MitigationUpdate the FunnelKit plugin to version 3.13.2 or later, which contains proper parameter escaping and prepared statement usage. Until patched, consider restricting access to the vulnerable endpoint or deploying a WAF rule to detect SQL injection patterns in the 'opid' 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 FunnelKit plugin version
    Log into WordPress admin and navigate to Plugins > Installed Plugins > FunnelKit, or use WP-CLI: `wp plugin list --name=funnelkit` or inspect the plugin header in wp-content/plugins/funnelkit-bwf/functions.php
    Affected if The displayed version is 3.13.1.5 or earlier (any version below 3.13.2)
  2. Identify the vulnerable endpoint
    Locate PHP files that handle the 'opid' parameter and execute SQL queries. Search plugin files for 'opid' usage in database queries, typically in AJAX handlers or REST API endpoints under /wp-json/
    Affected if The endpoint processes the 'opid' parameter directly in a SQL query without prepared statements or escaping
  3. Verify parameter handling in code
    Inspect the code handling the 'opid' parameter - look for $wpdb->prepare(), parameterized queries, or sanitization functions like esc_sql() or intval() applied to the 'opid' value before SQL execution
    Affected if The 'opid' parameter is used in SQL queries without proper escaping, prepared statements, or type casting (e.g., not wrapped in intval() or not using $wpdb->prepare())
  4. Check for time-based response delay
    Send a crafted request to the affected endpoint with 'opid' parameter containing SQL sleep commands (e.g., opid=1 AND SLEEP(5)) and measure response time - a 5+ second delay indicates the vulnerability is present
    Affected if The server response is delayed by approximately 5 seconds or more, confirming the SQL injection executes arbitrary time-based commands

You are affected if the FunnelKit plugin version is 3.13.1.5 or earlier AND the endpoint handling the 'opid' parameter is accessible and processes it in unsanitized SQL queries.

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.13.2 or later, which contains proper parameter escaping and prepared statement usage. Until patched, consider restricting access to the vulnerable endpoint or deploying a WAF rule to detect SQL injection patterns in the 'opid' parameter.

Recommended fix Moderate confidence

FunnelKit - Funnel Builder for WooCommerce Checkout version 3.13.1.6 or latest available

  1. Navigate to WordPress dashboard > Plugins > Installed Plugins
  2. Locate 'FunnelKit - Funnel Builder for WooCommerce Checkout'
  3. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org/plugins/funnelkit
  4. After updating, verify the plugin version is 3.13.1.6 or higher via the Plugins page
  5. Consider running a database security audit to check for any unauthorized changes

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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