Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain contributor-level account
-
DeliveryInject script into tab_index/empty_notice shortcode attribute
-
ExploitPayload stored unsanitized (bypasses wp_kses_post)
-
ExecutionVictim loads injected page
-
ImpactScript executes in victim browser session
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated WordPress account with contributor-level privileges or higher on a site running Avada (Fusion) Builder version ≤3.16.2. The attacker injects a script payload into the 'tab_index' or 'empty_notice' shortcode attribute; the flaw exists because wp_kses_post does not strip the payload on save, as the dangerous characters sit within shortcode attribute text between square brackets that kses treats as plain text rather than HTML markup. The stored payload executes only when a user subsequently accesses the injected page. Limiting factors: exploitation is gated by the required contributor+ account (self-registration must be possible or an account otherwise obtained), is confined to sites using the affected builder version, and yields XSS-level impact in a victim's browser rather than direct server compromise. |
| Impact | This is a genuine but moderate-priority issue, not a critical emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N, 6.4 Medium) shows network-reachable, low-complexity exploitation but requires PR:L - an authenticated contributor-level (or higher) account - which is the single biggest limiting factor. The scope change (S:C) and C:L/I:L reflect a classic stored XSS impact: script runs in another user's browser context rather than directly compromising the server. No CISA KEV listing, so the status is 'no public exploit identified at time of analysis'; there is no EPSS score in the supplied data and no confirmed proof-of-concept - the only references are a Wordfence threat-intelligence entry and the vendor's security-update blog, neither verified as working exploit code. No SSVC exploitation/automatable/technical-impact triple is provided; the only decision signal is the vuln.today priority label 'this_month', which is consistent with a medium-severity authenticated flaw rather than act-now urgency. Signals are therefore aligned and unremarkable: real but gated behind an authenticated account, best handled on a normal patch cycle. One cross-reference caveat: the affected component is 'Avada (Fusion) Builder' at version ≤3.16.2, yet the vendor fix reference points to an 'Avada 7.16.3 security update' - the product-suite release number, not the plugin number - so the exact fixed plugin build should be verified with the vendor. |
| Exploit ScenarioDerived | An attacker who holds (or registers/obtains) a contributor-level WordPress account on a site running Avada (Fusion) Builder ≤3.16.2 creates or edits a page and places a malicious script inside the 'tab_index' or 'empty_notice' shortcode attribute, where wp_kses_post treats the bracketed attribute text as plain text and does not strip it. When an administrator or other user later views that page, the stored script executes in their browser session. No public working exploit is confirmed in the supplied data, though a Wordfence vulnerability record exists. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
Stored cross-site scripting in the Avada (Fusion) Builder WordPress plugin (all versions up to and including 3.16.2) allows authenticated users with contributor-level access or higher to inject script payloads into the 'tab_index' and 'empty_notice' shortcode attributes, which then execute in the browser of any user viewing the injected page. The sanitization gap exists because wp_kses_post does not strip the payload on save - the dangerous characters sit inside shortcode attribute text between square brackets, which kses treats as plain text rather than HTML markup, so the stored content survives filtering. The assessed severity is moderate (CVSS 6.4, scope-changed, low confidentiality and integrity impact), no public exploit has been identified at time of analysis, and exploitation is gated by the need for a contributor-or-higher account on a site running an affected builder version.
RemediationAI
Update the Avada theme/plugin to the release carrying the vendor's 7.16.3 security update, which moves the bundled Fusion Builder past the affected 3.16.2 ceiling; confirm the installed builder version after updating and consult https://avada.com/blog/version-7-16-3-security-update/ for the vendor's instructions. Because exploitation requires contributor-level access or higher, reduce exposure in the meantime by auditing and restricting who holds contributor or higher roles, disabling self-registration on sites where untrusted users could otherwise obtain such an account, and reviewing existing posts and pages for suspicious tab_index or empty_notice shortcode attributes and re-saving or removing them. If updating cannot be done immediately, apply virtual patching or request-inspection rules that block script markup inside Fusion Builder shortcode attributes, accepting that such filters can produce false positives on legitimate shortcode content and do not repair already-stored payloads. Note that remediation should include checking stored content, since removing the vulnerable code alone does not clean payloads already persisted in the database.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The Avada (Fusion) Builder is a page-building plugin for WordPress that registers shortcodes; user-supplied content is stored as post content and later rendered when the page is viewed. This is a classic CWE-79 stored XSS arising from insufficient input sanitization combined with insufficient output escaping. The specific root cause is the interaction with WordPress's kses filtering: wp_kses_post is applied on save, but the payload is placed inside a shortcode attribute (tab_index, empty_notice) delimited by square brackets, and kses parses that region as shortcode/plain text rather than as HTML markup, so the dangerous characters are not stripped. The malicious script is therefore persisted and fires when the page is rendered in a victim's browser, giving attacker-controlled JavaScript execution in the site's origin for any user who opens the injected page.
Know when Avada Fusion Builder gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Network-reachable low-complexity injection needing a contributor account (PR:L); stored XSS crosses into the victim's browser (S:C) with limited confidentiality/integrity and no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Avada (Fusion) Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'tab_index, empty_notice' parameter in all versions up to, and including, 3.16.2 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. wp_kses_post does not strip the payload on save because the dangerous characters reside within shortcode attribute text between square brackets, which kses treats as plain text rather than HTML markup.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Avada Fusion Builder
View allUnauthenticated remote code execution in the Avada Builder (fusion-builder) WordPress plugin versions up to and includin
Arbitrary file deletion in the Avada (Fusion) Builder WordPress plugin through version 3.15.3 allows remote unauthentica
Unauthenticated arbitrary file write in the Avada WordPress theme (versions up to and including 7.16) combined with the
Unauthenticated attackers can trigger arbitrary WordPress action hooks on sites running the Avada (Fusion) Builder plugi
Time-based SQL injection in Avada Builder for WordPress allows remote unauthenticated attackers to extract sensitive dat
Arbitrary file read in Avada Builder plugin for WordPress versions up to 3.15.2 allows authenticated attackers with Subs
Stored Cross-Site Scripting in the Avada (Fusion) Builder WordPress plugin through version 3.15.6 allows authenticated c
Stored Cross-Site Scripting in Avada (Fusion) Builder for WordPress (all versions through 3.15.2) allows authenticated a
Stored Cross-Site Scripting in the Avada (Fusion) Builder WordPress plugin versions up to 3.15.5 allows authenticated co
Arbitrary WordPress action execution in Avada (Fusion) Builder plugin versions up to 3.15.1 allows authenticated attacke
Unauthenticated information disclosure in the Avada (Fusion) Builder WordPress plugin (all versions up to and including
Avada (Fusion) Builder plugin for WordPress up to version 3.15.1 allows authenticated Subscriber-level users and above t
EUVD-2026-111753
GHSA-w8x6-5chw-44wx
NVD
CVE.org
EPSS
Exploit-DB