CVE-2026-42381
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 · uneditedUnauthenticated SQL Injection in Funnel Builder by FunnelKit <= 3.15.0.1 versions.
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 confidenceUnauthenticated SQL Injection vulnerability in Funnel Builder by FunnelKit WordPress plugin affecting versions up to 3.15.0.1. Attackers can inject malicious SQL queries without any authentication due to improper input sanitization, potentially allowing full database compromise, data exfiltration, or site takeover.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify Funnel Builder plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Funnel Builder by FunnelKit' or 'FunnelKit' in the plugin list. Check if it is activated.Affected if The plugin is installed and activated
-
Identify installed plugin versionIn the plugin list, click on the plugin name or view the plugin details. Locate the version number displayed (e.g., 'Version 3.15.0.1' or earlier). Compare this against the affected range.Affected if Installed version is 3.15.0.1 or any earlier version (any version up to and including 3.15.0.1)
-
Confirm plugin handles user inputReview the site to determine if the Funnel Builder plugin is publicly accessible. Since this is an unauthenticated SQL injection, the vulnerability can be exploited without any user credentials or login.Affected if The plugin is active and accessible to unauthenticated users on the site
-
Check access logs for SQL injection patternsReview server access logs (Apache error.log, access.log, or Nginx access.log) for unusual query patterns involving SQL keywords (UNION, SELECT, INSERT, DROP) in parameters that may relate to FunnelKit or funnel builder endpoints.Affected if Suspicious SQL-related request patterns are found in logs targeting the plugin
A user is affected if the Funnel Builder by FunnelKit plugin is installed with any version up to and including 3.15.0.1, as this version range contains the unauthenticated SQL injection vulnerability.
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.
dbcve · scopedUpdate Funnel Builder by FunnelKit to the latest version as soon as a vendor patch is released. As a temporary measure, consider disabling the plugin if an immediate update is unavailable, or implement WAF rules to block SQL injection attack patterns.
Funnel Builder by FunnelKit version 3.15.1 or later (latest stable release)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate 'Funnel Builder by FunnelKit' (also known as FunnelKit)
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. Alternatively, download the latest version from wordpress.org/plugins/funnelkit and upload via Plugins > Add New > Upload Plugin
- 6. After updating, verify the plugin is running the most recent version under Plugins > Installed Plugins
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42381 — 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-42381 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