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

CVE-2026-1543

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-21
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

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 multiple shortcodes in all versions up to, and including, 3.15.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user (typically an administrator) accesses a page displaying dynamic user data (such as via the Dynamic Data feature pulling user biographical information).

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 plugin for WordPress versions up to 3.15.2 contains a stored XSS vulnerability in multiple shortcodes due to insufficient input sanitization and output escaping. Authenticated attackers with Subscriber-level permissions can inject malicious JavaScript through shortcode parameters, which executes when other users (typically administrators) view pages containing dynamic user data such as user biographical information.

MitigationUpdate the Avada plugin to a version beyond 3.15.2 when available. Until then, consider restricting subscriber-level access to shortcode usage or deploying a WAF to block XSS payloads.

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. Verify Avada Fusion Builder is installed
    Check WordPress plugins directory for 'Avada' or 'Fusion Builder' plugin. Access via wp-admin > Plugins, or inspect plugin files in /wp-content/plugins/ directory.
    Affected if Plugin is present in the WordPress installation
  2. Determine installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Avada Fusion Builder and note the version number displayed. Alternatively, check the main plugin file (e.g., fusion-builder.php) for the 'Version' header comment.
    Affected if Version is 3.15.2 or earlier (any version up to and including 3.15.2)
  3. Identify use of Dynamic Data in shortcodes
    Search post/page content for shortcodes containing fusion_builder_ or dynamic data attributes (such as dynamic_params, dynamic_value, or user_bio-related parameters). Inspect page content via WordPress editor or directly in wp_posts database table.
    Affected if Shortcodes with Dynamic Data attributes are present in published content
  4. Inspect shortcode parameters pulling user biographical info
    Review shortcode implementations that reference user biographical fields (such as author bio, user description, or user meta fields). Check the actual shortcode output in page source for any user-supplied values in attributes.
    Affected if Shortcodes reference dynamic user data without proper escaping in their attributes
  5. Examine page output for injected script payloads
    View source of pages containing Fusion Builder shortcodes with Dynamic Data. Look for unescaped HTML/script tags within shortcode attribute values, particularly in data-* attributes or href/src parameters.
    Affected if Raw script tags, event handlers (onload, onclick), or malformed HTML appear in the rendered page source within shortcode-rendered elements

User is affected if Avada Fusion Builder version 3.15.2 or earlier is installed AND Dynamic Data shortcodes pulling user biographical information are in use 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Avada plugin to a version beyond 3.15.2 when available. Until then, consider restricting subscriber-level access to shortcode usage or deploying a WAF to block XSS payloads.

Recommended fix Moderate confidence

Latest version of Avada (Fusion) Builder plugin after 3.15.2

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Avada (Fusion) Builder plugin
  4. Check the current installed version to confirm it is 3.15.2 or below
  5. Navigate to Updates or go to Plugins > Add New > Upload (if using a manual update method)
  6. Update the Avada plugin to the latest available version
  7. Verify the update completed successfully
  8. Clear any caching mechanisms if the site uses caching plugins or server-side caching
Caveat Review Avada theme/plugin changelog for any breaking changes between your current version and the latest version before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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