Skip to main content

Avada WordPress Theme CVE-2026-84925

| EUVDEUVD-2026-91174 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-10-02 Wordfence GHSA-7hr3-mm9w-ghgw
6.1
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft URL with script in 'lang' parameter
  2. Delivery
    Phish victim to click link
  3. Exploit
    lang value reflected unescaped into href
  4. Execution
    Script executes in victim's browser session
  5. Impact
    Steal session/credentials or act as user

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

Exploitation requires that the target site run the Avada theme version 7.16.1 or earlier and that a victim with access to the post editor (typically an authenticated contributor/author/editor/administrator) be tricked into clicking an attacker-crafted link carrying a malicious 'lang' query parameter. The payload only executes when the reflected value reaches the post-editor metabox href attribute, so the victim must navigate to/render that editor context. Limiting factors: the attack is reflected (not stored/persistent), so it is per-link and non-automatable against the server; it requires user interaction (UI:R) and successful social engineering; and impact is confined to the victim's browser security context rather than direct server compromise. No special server-side configuration toggle is named in the description beyond running the affected theme version.

Impact

This is a reflected Cross-Site Scripting flaw (CWE-79) with a CVSS 3.1 base score of 6.1 (Medium). The provided vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N indicates a network-reachable, low-complexity, unauthenticated attack that nevertheless requires user interaction (victim must click a crafted link), with a changed scope and limited confidentiality/integrity impact and no availability impact - a signal profile entirely consistent with reflected XSS. No EPSS score was supplied, the CVE is NOT on the CISA KEV list, and no public proof-of-concept is indicated in the sources, so exploitation status is 'no public exploit identified at time of analysis.' The absence of KEV/EPSS/POC signals, combined with the mandatory user-interaction requirement, makes this a real but moderate-priority issue rather than an urgent mass-exploitation threat: it cannot be automated against servers directly and depends on social engineering of an individual victim. There is no conflict between the CVSS vector and the description - both describe unauthenticated, network-delivered, user-interaction-dependent reflected XSS. Priority rises for sites running the affected Avada versions given the theme's very large install base, but the technical ceiling (session/credential theft within the victim's browser context, not server compromise) should temper urgency.

Exploit ScenarioDerived

An attacker crafts a URL pointing at a vulnerable Avada site with a malicious script embedded in the 'lang' parameter and sends it to a logged-in administrator or editor via phishing. When the victim clicks the link and the value is echoed unescaped into the href attribute of the post-editor metabox, the injected JavaScript executes in the victim's authenticated browser session, enabling session/cookie theft or actions on their behalf. No public exploit code is identified at time of analysis, and successful exploitation hinges on the victim clicking the attacker-supplied link.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 02, 2026

Reflected cross-site scripting in the Avada theme for WordPress (Website Builder For WordPress & WooCommerce) affects all versions up to and including 7.16.1, allowing an unauthenticated attacker to inject arbitrary script into the post-editor metabox by convincing a user who can access that editor to click a crafted link carrying a malicious 'lang' query parameter. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N, base 6.1) confirms the attack is network-reachable without attacker credentials but requires victim interaction, and the changed scope (S:C) reflects that the injected script executes in the victim's browser session rather than compromising the server directly. No public exploit code was identified at time of analysis and there is no CISA KEV entry, so this should be treated as a medium-severity, social-engineering-dependent flaw rather than an actively exploited one. Assessed risk: this is a reflected Cross-Site Scripting flaw (CWE-79) with a CVSS 3.1 base score of 6.1 (Medium).

RemediationAI

No vendor-released patch version is identified in the available data, so the authoritative next step is to check ThemeFusion's official Avada changelog (https://classic.avada.com/documentation/avada-changelog/) and the Wordfence disclosure (https://www.wordfence.com/threat-intel/vulnerabilities/id/4c3936aa-58d6-4ac0-a077-2faaed48828f?source=cve) for a release above 7.16.1 and upgrade to the earliest version that explicitly lists this fix; because theme updates are shipped through the vendor's updater or a manual package replacement, verify the installed theme version after updating rather than assuming auto-update succeeded. Until a fixed build is deployed, compensating controls should target the specific sink: enforce a Content-Security-Policy that disallows inline and third-party script on wp-admin pages (script-src 'self' without 'unsafe-inline'), which neutralizes the attribute-breakout payload but may break admin UI components and requires careful allowlisting; restrict post-editor access to trusted, vetted accounts and lower the number of contributor/author users who can be socially engineered, accepting the operational cost of tighter publishing workflow; and deploy a WAF or WordPress security plugin rule that rejects or strips requests containing script-like content in the 'lang' parameter on theme/admin endpoints, understanding that such signatures are easily evaded and are a stopgap only. Because this is reflected rather than stored XSS, there is no server-side persistence to clean up after a suspected click, but any user who followed a malicious link should be advised to rotate their WordPress session and review recent administrative changes.

Affected VersionsENISA

Avada | Website Builder For WordPress & WooCommerce 0 ≤7.16.1

Affected Packages

euvd avada_website_builder_for_wordpress_woocommerce no fix

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 root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation), specifically a reflected XSS arising from an unsanitized request parameter that is carried through the Avada theme's own multilingual and settings helper classes. The 'lang' value is taken in by Fusion_Multilingual::set_active_language() and then propagated into a link built by Fusion_Settings::get_setting_link(); at no point is it passed through urlencode(), esc_url(), or esc_attr() before being concatenated into a URL. That URL is subsequently echoed raw into a double-quoted href attribute inside the post editor metabox, which is exactly the sink pattern that permits attribute-breakout payloads. Because the reflection occurs in an administrative editor context, injected script inherits the privileges of whatever WordPress user opens the crafted link (contributor, author, editor, or administrator), which is why the CVSS vector assigns S:C even though confidentiality and integrity impacts are limited (C:L/I:L) and availability is unaffected. The affected CPE (cpe:2.3:a:themefusion:avada_|_website_builder_for_wordpress_&_woocommerce) identifies ThemeFusion's Avada theme, a commercial WordPress/WooCommerce page-builder theme that ships its own Fusion Builder and Fusion Settings components rather than relying solely on core WordPress APIs; the flaw therefore lives in theme-shipped PHP rather than in WordPress core. Reflected XSS of this kind is per-link, non-persistent, and cannot be automated server-side, which distinguishes it from stored XSS in the same editor surface.

Know when Avada Website Builder For Wordpress Woocommerce 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

Vendor (Wordfence) PRIMARY 6.1 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
vuln.today AI 6.1 MEDIUM

Unauthenticated network-delivered reflected XSS needing victim click gives AV:N/AC:L/PR:N/UI:R; cross-context script execution yields S:C with limited C/I and no availability impact.

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionCVE.org

The Avada | Website Builder For WordPress & WooCommerce theme for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'lang' parameter in all versions up to, and including, 7.16.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. The injected value is propagated through Fusion_Multilingual::set_active_language() and concatenated into a URL by Fusion_Settings::get_setting_link() without applying urlencode(), esc_url(), or esc_attr() before being echoed raw into a double-quoted href attribute in the post editor metabox.

Threat Intelligence Overview

EPSS Score
0.2%
Top 94% exploitable
Prevalence
High
Avada is a top-selling, very widely deployed premium WordPress theme
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
High
Technical Impact
Partial

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +30
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy