CVE-2026-48966
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 Cross Site Scripting (XSS) in Funnel Builder by FunnelKit <= 3.15.0.2 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 Cross Site Scripting (XSS) vulnerability in Funnel Builder by FunnelKit plugin for WordPress, affecting versions 3.15.0.2 and below. An attacker can inject malicious JavaScript code without authentication, potentially compromising site users or administrators.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Check if Funnel Builder by FunnelKit is installedNavigate to WordPress admin > Plugins and locate 'Funnel Builder by FunnelKit' in the installed plugins list, or inspect the directory wp-content/plugins/ for a funnel-builder or funnelkit folderAffected if The plugin folder exists in the plugins directory
-
Verify the installed version numberIn WordPress admin > Plugins, click on the FunnelKit plugin to view the version displayed, or open the main plugin PHP file (such as funnel-builder.php or functions.php inside the plugin folder) and read the Version header commentAffected if The displayed version is 3.15.0.2 or any version lower than 3.15.0.2
-
Confirm the plugin is activeIn WordPress admin > Plugins, check that the plugin status shows as 'Active' rather than 'Inactive'Affected if The plugin is enabled and running on the WordPress site
-
Identify if public endpoints are accessibleTest if the plugin exposes public-facing routes - common paths include /wp-json/funnelkit/ or /?funnelkit=... - attempt a curl or browser request to these endpoints to confirm they respond without requiring loginAffected if The plugin public endpoints are reachable without authentication
The environment is affected if Funnel Builder by FunnelKit is installed, active, and running version 3.15.0.2 or below, with public endpoints exposed without authentication.
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 immediately. Until patched, restrict access to the plugin endpoints via firewall rules or disable the plugin if unnecessary.
Funnel Builder by FunnelKit version 3.15.1.0 or later (latest stable release)
- 1. Navigate to the WordPress admin dashboard.
- 2. Go to Plugins > Installed Plugins.
- 3. Locate 'Funnel Builder by FunnelKit' (also known as FunnelKit).
- 4. Check the current version number displayed under the plugin name.
- 5. If the installed version is 3.15.0.2 or lower, update the plugin to the latest available version.
- 6. Alternatively, navigate to Dashboard > Updates and check for available updates for FunnelKit plugins.
- 7. After updating, verify the new version number to confirm the upgrade was successful.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48966 — 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-48966 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