Avada <= 7.16 and Fusion Builder <= 3.16 - Unauthenticated Remote Code Execution via Arbitrary File Write
Strategic Overview
- Status
- Patched in 3.16.1
- Affected Plugin
- Avada (Fusion) Builder
- Affected Version
<= 3.16- CVSS
- 9.8Critical
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-18431
At a glance
CVE-2026-18431 is a critical-severity Missing Authorization vulnerability in the Avada (Fusion) Builder WordPress plugin, affecting versions <= 3.16. 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.16.1; sites on affected versions should update now. Disclosed August 2026, reported by Alex Thomas.
Vulnerability Overview
The Avada theme for WordPress is vulnerable to Arbitrary File Write in all versions up to, and including, 7.16 when the Fusion Builder plugin is installed and active in versions up to, and including, 3.16. This is due to a chain of authorization and input validation weaknesses across the two components that makes it possible for unauthenticated attackers to write attacker-controlled files to the server. This can be used to create and execute arbitrary PHP files, resulting in remote code execution and complete site compromise. Successful exploitation requires both Avada and Fusion Builder to be installed and active, as well as certain administrator-authored content to be present.
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-862: Missing Authorization
Reaching this weakness in Avada (Fusion) Builder <= 3.16 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Avada (Fusion) Builder the fix is 3.16.1: builds <= 3.16 are affected, anything from 3.16.1 onward is not.
Remediation
Update to version 3.16.1, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Avada (Fusion) Builder 3.16.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- 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