Avada (Fusion) Builder <= 3.15.1 - Authenticated (Subscriber+) Limited Arbitrary WordPress Action Execution
Strategic Overview
- Status
- Patched in 3.15.2
- Affected Plugin
- Avada (Fusion) Builder
- Affected Version
<= 3.15.1- CVSS
- 5.4Medium
- Weakness type
- CWE-94 · Improper Control of Generation of Code ('Code Injection')
- CVE
CVE-2026-1509
At a glance
CVE-2026-1509 is a medium-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Avada (Fusion) Builder WordPress plugin, affecting versions <= 3.15.1. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.15.2; sites on affected versions should update now. Disclosed April 2026, reported by Webbernaut.
Vulnerability Overview
The Avada (Fusion) Builder plugin for WordPress is vulnerable to Arbitrary WordPress Action Execution in all versions up to, and including, 3.15.1. This is due to the plugin's `output_action_hook()` function accepting user-controlled input to trigger any registered WordPress action hook without proper authorization checks. This makes it possible for authenticated attackers, with Subscriber-level access and above, to execute arbitrary WordPress action hooks via the Dynamic Data feature, potentially leading to privilege escalation, file inclusion, denial of service, or other security impacts depending on which action hooks are available in the WordPress installation.
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 interaction from a victim user.
CWE-94: Improper Control of Generation of Code ('Code Injection')
Avada (Fusion) Builder <= 3.15.1 carries this weakness at output_action_hook(), and reaching it takes an account at Subscriber level or above. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.
The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For Avada (Fusion) Builder the fix is 3.15.2: builds <= 3.15.1 are affected, anything from 3.15.2 onward is not.
Remediation
Update to version 3.15.2, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Avada (Fusion) Builder 3.15.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Avada (Fusion) Builder
- 9.8CVE-2026-6279: Avada (Fusion) Builder <= 3.15.2 Remote Code Execution
CVE-2026-6279 - 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
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C