dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-47100

HIGH · 7.5 CVSS v3.1 Published 2026-05-19
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
Funnel Builder for WooCommerce Checkout prior to 3.15.0.3 contains a missing authorization vulnerability in the public checkout endpoint that allows unauthenticated attackers to invoke internal methods and write arbitrary data to the plugin's External Scripts global setting. Attackers can inject malicious JavaScript through the External Scripts setting that executes in the browsers of all checkout page visitors.

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 Funnel Builder for WooCommerce Checkout plugin prior to 3.15.0.3 has a missing authorization vulnerability in its public checkout endpoint. Unauthenticated attackers can invoke internal methods and write arbitrary data to the plugin's External Scripts global setting, allowing injection of malicious JavaScript that executes in the browsers of all checkout page visitors.

MitigationUpdate to version 3.15.0.3 or later immediately. Additionally, audit the External Scripts setting for any existing malicious injections and clear browser caches for affected users.

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Confirm Funnel Builder for WooCommerce Checkout is installed
    Navigate to WordPress Admin > Plugins and locate 'Funnel Builder for WooCommerce Checkout' in the installed plugins list, or check the plugin header file (usually in wp-content/plugins/funnel-builder-for-woocommerce-checkout or similar path) for the Version header
    Affected if The plugin is installed and the version is earlier than 3.15.0.3
  2. Locate the plugin version number
    In WordPress Admin > Plugins, click on the plugin to view details and read the Version field, or open the main plugin PHP file and search for 'Version:' in the plugin header comment
    Affected if The displayed version is below 3.15.0.3 (for example, 3.14.x, 3.13.x, etc.)
  3. Inspect the External Scripts global setting
    Go to the plugin settings area in WordPress Admin (typically under WooCommerce > Funnel Builder or a similar menu path) and locate the External Scripts or Custom Scripts field. View the page source or inspect the input to see if any script tags are present in the value
    Affected if The External Scripts setting contains script tags with unfamiliar or suspicious URLs, especially if they were not added by your team
  4. Check WordPress options database for injected scripts
    Use a database tool or WordPress plugin to query the wp_options table for any option_name containing 'external_script', 'custom_script', or 'funnel' related settings. Examine the option_value for any script tags, especially those using eval(), document.write(), or external domains
    Affected if Any option value contains JavaScript that was not intentionally configured by administrators

Your environment is affected if the Funnel Builder for WooCommerce Checkout plugin is installed with a version lower than 3.15.0.3, or if the External Scripts setting contains unauthorized JavaScript code.

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 to version 3.15.0.3 or later immediately. Additionally, audit the External Scripts setting for any existing malicious injections and clear browser caches for affected users.

Recommended fix High confidence

Funnel Builder for WooCommerce Checkout version 3.15.0.3

  1. Update the Funnel Builder for WooCommerce Checkout plugin to version 3.15.0.3 or later via the WordPress plugin dashboard or wp-cli plugin update command
  2. Verify the update was successfully applied by checking the plugin version number
  3. If the site may have been compromised prior to patching, review and sanitize the plugin's External Scripts global settings to remove any injected malicious JavaScript code

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
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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-2026-47100 — 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-2026-47100 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