Avada (Fusion) Builder <= 3.15.2 - Unauthenticated Remote Code Execution via PHP Function Injection via 'render_logics' Shortcode Attribute via Widget AJAX Handler
Strategic Overview
- Status
- Patched in 3.15.3
- Affected Plugin
- Avada (Fusion) Builder
- Affected Version
<= 3.15.2- CVSS
- 9.8Critical
- Weakness type
- CWE-74 · Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
- CVE
CVE-2026-6279
At a glance
CVE-2026-6279 is a critical-severity Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in the Avada (Fusion) Builder WordPress plugin, affecting versions <= 3.15.2. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.15.3; sites on affected versions should update now. Disclosed May 2026, reported by Tin Pham (TF1T).
Vulnerability Overview
The Avada Builder (fusion-builder) plugin for WordPress is vulnerable to Unauthenticated Remote Code Execution via PHP Function Injection in versions up to and including 3.15.2. This is due to the `wp_conditional_tags` case in `Fusion_Builder_Conditional_Render_Helper::get_value()` passing attacker-controlled values from a base64-decoded JSON blob directly to `call_user_func()` without any allowlist validation. This is exploitable by unauthenticated attackers through the `fusion_get_widget_markup` AJAX endpoint, which is registered for non-privileged (unauthenticated) users via `wp_ajax_nopriv_fusion_get_widget_markup`. The endpoint is protected only by a nonce (`fusion_load_nonce`), but this nonce is generated for user ID 0 and is deterministically exposed in the JavaScript output of any public-facing page containing a Post Cards (`[fusion_post_cards]`) or Table of Contents (`[fusion_table_of_contents]`) element. This makes it possible for unauthenticated attackers to execute arbitrary code on affected sites.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
Remediation
Update to version 3.15.3, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Avada (Fusion) Builder 3.15.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Avada (Fusion) Builder
- 9.1CVE-2026-8713: Avada (Fusion) Builder Arbitrary File Deletion
CVE-2026-8713 - 8.8CVE-2026-56008: Avada (Fusion) Builder <= 3.15.4 Privilege Escalation
CVE-2026-56008 - 8.8CVE-2023-39309: Fusion Builder <= 3.11.1 SQL Injection
CVE-2023-39309 - 8.3CVE-2022-1386: Fusion Builder & Avada <= 7.6.1 - Unauthenticated SSRF
CVE-2022-1386 - 8.1CVE-2026-54193: Avada (Fusion) Builder Arbitrary File Deletion
CVE-2026-54193 - 7.5CVE-2026-54194: Avada (Fusion) Builder <= 3.15.4 PHP Object Injection
CVE-2026-54194 - 7.5CVE-2026-4798: Avada Builder <= 3.15.1 SQL Injection
CVE-2026-4798 - 7.3CVE-2024-13345: Avada Builder <= 3.11.13 Arbitrary Shortcode Execution
CVE-2024-13345
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C