dbcve.org
Funnel BuilderWordPress extension · Funnelkit

CVE-2024-1056

MEDIUM · 5.4 CVSS v3.1 Published 2024-08-29
Fix available
A fix is available. Upgrade to 3.5.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Pro plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'allow_iframe_tag_in_post' function which uses the 'wp_kses_allowed_html' filter to globally allow script and iframe tags in posts in all versions up to, and including, 3.4.5. This makes it possible for authenticated attackers, with contributor access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Funnel Builder Pro plugin for WordPress contains a stored XSS vulnerability in versions up to 3.4.5. The 'allow_iframe_tag_in_post' function misuses the 'wp_kses_allowed_html' filter to globally enable script and iframe tags in post content, allowing authenticated contributors and above to inject malicious JavaScript that executes when users view affected pages.

MitigationUpdate to plugin version 3.4.6 or later which patches the unsafe wp_kses_allowed_html filter modification; alternatively, remove or restrict the allow_iframe_tag_in_post function if the update is unavailable.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Funnel BuilderWordPress extension
Affected:< 3.5.0

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Verify FunnelKit Funnel Builder plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'FunnelKit Funnel Builder' or 'FunnelKit Funnel Builder Pro'. Note the installed version number displayed.
    Affected if Plugin is installed with version less than 3.5.0 (e.g., 3.4.5, 3.4.0, etc.)
  2. Confirm the vulnerable function exists in the codebase
    Check the plugin files for the presence of the 'allow_iframe_tag_in_post' function. This is typically found in includes or core plugin files. Search the plugin directory for the function name using a file search or grep tool.
    Affected if The allow_iframe_tag_in_post function is present in the plugin files (indicates the vulnerable code path exists)
  3. Check if contributor or author user accounts exist
    Navigate to WordPress admin > Users and review the user list. Identify any users with the 'Contributor', 'Author', 'Editor', or 'Administrator' role, as these roles can access post content creation.
    Affected if At least one user with Contributor, Author, Editor, or Administrator role exists on the site who could potentially exploit the XSS vulnerability

You are affected if the FunnelKit Funnel Builder plugin is installed with a version below 3.5.0 AND the allow_iframe_tag_in_post function exists in the plugin AND user accounts with contributor-level access or higher exist on the site.

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
Upgrade available Upgrade to 3.5.0 or later
Fixed in 3.5.0
Interim mitigation

Update to plugin version 3.4.6 or later which patches the unsafe wp_kses_allowed_html filter modification; alternatively, remove or restrict the allow_iframe_tag_in_post function if the update is unavailable.

Recommended fix High confidence

3.5.0 or later

  1. Update the FunnelKit Funnel Builder Pro plugin for WordPress to version 3.5.0 or later to resolve the stored XSS vulnerability.
  2. After upgrading, verify that the 'allow_iframe_tag_in_post' function no longer globally allows script and iframe tags via the wp_kses_allowed_html filter.
  3. Test that contributor-level users can no longer inject arbitrary JavaScript via the plugin's funnel or page editing features.

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

Fix this in Funnel Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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