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

CVE-2026-12536

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

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 Avada (Fusion) Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘Module Title’ parameter in all versions up to, and including, 3.15.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level 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 Avada Fusion Builder WordPress plugin is vulnerable to stored Cross-Site Scripting (XSS) in the 'Module Title' parameter. Insufficient input sanitization and output escaping allows authenticated users with Contributor-level access or higher to inject arbitrary JavaScript that executes when other users access affected pages.

MitigationUpdate the Avada Fusion Builder plugin to version 3.15.6 or later to receive the security patch; review existing pages for malicious Module Title content and remove injected scripts.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Confirm Avada Fusion Builder is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Avada Fusion Builder' in the list. Note the installed version number displayed.
    Affected if Plugin is not installed or not found in the plugins list
  2. Check installed version against fixed release
    Compare the noted version number to version 3.15.6. The plugin is potentially vulnerable if the installed version is lower than 3.15.6.
    Affected if Installed version is below 3.15.6
  3. Identify Contributor-level or higher users
    Navigate to Users > All Users in WordPress admin. Review the role column for any users assigned 'Contributor', 'Author', 'Editor', or Administrator roles.
    Affected if At least one user with Contributor-level or higher access exists in the system
  4. Inspect Module Title fields in Fusion Builder content
    Edit any page or post using the Fusion Builder. In any Fusion Builder element (such as fusion_text, fusion_button, fusion_alert, etc.), locate the 'Module Title' field in the element settings. Check for any unexpected HTML tags, JavaScript code, or suspicious scripts entered in this field.
    Affected if Malicious script tags or JavaScript code are present in any Module Title field
  5. Review published pages for injected content
    Visit published pages that use Fusion Builder elements with Module Titles enabled. Inspect the page source or use browser developer tools to examine if the Module Title text contains unescaped HTML attributes or script execution.
    Affected if Module Title content renders as executable JavaScript or contains unsanitized HTML when viewed on the frontend

A user is affected if the Avada Fusion Builder version is below 3.15.6, the site has users with Contributor-level access or higher, and Fusion Builder elements with Module Title fields are in use.

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 the Avada Fusion Builder plugin to version 3.15.6 or later to receive the security patch; review existing pages for malicious Module Title content and remove injected scripts.

Recommended fix Moderate confidence

Version 3.15.6 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the Avada (Fusion) Builder plugin
  4. 4. Check the current version to confirm it is 3.15.5 or below
  5. 5. Update the plugin to the latest available version (3.15.6 or higher)
  6. 6. Verify the update was successful
  7. 7. Clear any caching layers if applicable
  8. 8. Test that the Module Title field properly sanitizes special characters

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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