dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-32542

HIGH · 7.1 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in ThemeFusion Fusion Builder fusion-builder allows Reflected XSS.This issue affects Fusion Builder: from n/a through < 3.15.0.

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 · moderate confidence

Reflected XSS vulnerability in ThemeFusion Fusion Builder allows attackers to inject malicious scripts through unsanitized user input that gets reflected in web pages. The vulnerability exists in versions prior to 3.15.0 and stems from improper input neutralization during page generation.

MitigationUpgrade Fusion Builder to version 3.15.0 or later to obtain the patch. As interim measures, implement WAF rules and validate/sanitize all user inputs before rendering.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Fusion Builder installation
    Check WordPress wp-content/plugins/ or wp-content/themes/ for the Fusion Builder plugin or theme folder. In the WordPress admin, navigate to Plugins > Installed Plugins and look for 'Fusion Builder' or check the theme version if bundled with Avada theme.
    Affected if Fusion Builder is not found in the WordPress installation
  2. Identify installed Fusion Builder version
    If using the plugin: check the plugin file header in fusion-builder.php for 'Version:' or view the plugin details in WordPress admin Plugins page. If bundled with Avada theme: check wp-content/themes/avada/functions.php or style.css for the version comment.
    Affected if Version cannot be determined or is lower than 3.15.0
  3. Compare version to affected range
    Compare the identified version number to the affected range: versions prior to 3.15.0 are vulnerable. Any version like 3.14.x, 3.13.x, 3.0.x etc. falls within the affected range.
    Affected if Installed version is 3.14.x or lower, or any version prior to 3.15.0
  4. Determine if user input forms are in use
    Check if any pages or templates created with Fusion Builder contain input fields, contact forms, or URL parameters that could be reflected back to users. Review page content for Fusion Builder elements that accept user data.
    Affected if Fusion Builder pages accept and reflect user input without sanitization (the vulnerability requires this condition to be exploitable)

The environment is affected if Fusion Builder is installed with a version prior to 3.15.0 and the builder is actively used to render pages that accept user input.

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

Upgrade Fusion Builder to version 3.15.0 or later to obtain the patch. As interim measures, implement WAF rules and validate/sanitize all user inputs before rendering.

Recommended fix High confidence

Fusion Builder 3.15.0

  1. 1. Identify the currently installed version of ThemeFusion Fusion Builder in your WordPress installation.
  2. 2. If the installed version is lower than 3.15.0, plan for an upgrade to version 3.15.0 or later.
  3. 3. Before upgrading, perform a full backup of your WordPress site including database and files.
  4. 4. Test the upgrade in a staging environment first to ensure compatibility with your theme and plugins.
  5. 5. Apply the upgrade through your WordPress dashboard or by downloading the latest version from ThemeFusion.
  6. 6. Verify the fix by confirming the Fusion Builder version is now 3.15.0 or higher.
  7. 7. Test the affected functionality to ensure the XSS vulnerability is no longer exploitable.
Caveat Review ThemeFusion release notes for any breaking changes between your current version and 3.15.0, particularly regarding backward compatibility with Avada theme

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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