CVE-2026-56052
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in FunnelKit Funnel Builder by FunnelKit allows Blind SQL Injection. This issue affects Funnel Builder by FunnelKit: from n/a through 3.15.0.5.
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 confidenceA blind SQL injection vulnerability exists in FunnelKit Funnel Builder plugin for WordPress versions up to 3.15.0.5. The vulnerability allows unauthenticated attackers to inject malicious SQL queries through improperly sanitized user input, potentially enabling data exfiltration from the database.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm FunnelKit Funnel Builder plugin is installedLog in to WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'FunnelKit Funnel Builder' or 'FunnelKit' in the plugin list. Alternatively, check for the plugin directory in wp-content/plugins/ for folders containing 'funnelkit' or 'funnel-builder'.Affected if The plugin is present in the WordPress installation
-
Identify the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and click on the FunnelKit Funnel Builder plugin to view its details, which typically display the version number. Alternatively, check the main plugin PHP file for a 'Version' header comment, or inspect the plugin's main class file for a version constant.Affected if The installed version is 3.15.0.5 or any earlier version
-
Determine if the plugin is exposed publiclyCheck if the WordPress site is publicly accessible and the plugin endpoints are reachable without authentication. Test common FunnelKit API endpoints such as /wp-json/funnelkit/v1/ or any custom AJAX endpoints the plugin exposes. Use a web browser or curl to request these routes without providing authentication headers.Affected if The plugin REST API or AJAX endpoints are accessible without authentication on a public-facing site
-
Review access logs for suspicious SQL-like patternsExamine web server access logs (Apache, Nginx) for incoming requests to FunnelKit endpoints containing SQL keywords such as UNION, SELECT, INSERT, or boolean operators like AND 1=1. Search logs for requests to known plugin endpoints that may accept user input.Affected if Unusual SQL-related patterns appear in requests to FunnelKit endpoints in the logs
A WordPress site is affected if it has FunnelKit Funnel Builder installed with version 3.15.0.5 or lower and the plugin endpoints are accessible to unauthenticated users.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate FunnelKit Funnel Builder to the latest version beyond 3.15.0.5 which contains the patched code. If no update is available, implement Web Application Firewall (WAF) rules to block SQL injection attempts as a temporary measure.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56052 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-56052 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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