Summary
CVE-2026-18431 is a critical arbitrary file write vulnerability affecting the Avada WordPress theme (versions up to and including 7.16) when used together with the Fusion Builder plugin (versions up to and including 3.16). Unauthenticated attackers can exploit a chain of authorization and input validation weaknesses spanning both components to write attacker-controlled files to the server, which can then be used to create and execute arbitrary PHP code. The flaw is rated CRITICAL with a CVSS v3.1 base score of 9.8.
Technical details
- Root cause: a combination of missing authorization (CWE-862) and insufficient input validation across the Avada theme and its bundled Fusion Builder plugin.
- Trigger conditions: both Avada and Fusion Builder must be installed and active, and certain administrator-authored content must be present on the site.
- Attack vector: network-based, requires no authentication and no user interaction (AV:N/AC:L/PR:N/UI:N).
- Impact: attacker-controlled files can be written to the server; combined with the ability to create and execute PHP files, this leads to remote code execution and full site compromise (confidentiality, integrity, and availability impact all rated High).
Affected software
- Avada (Fusion) Builder plugin: versions ≤ 3.16
- Avada | Website Builder for WordPress & WooCommerce (theme): versions ≤ 7.16
- Exploitation requires both components to be installed and active together.
Severity
- CVSS v3.1 Base Score: 9.8 (Critical)
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: Update the Avada theme and Fusion Builder plugin to the latest available versions beyond 7.16/3.16. ThemeFusion has released Avada 7.16.1, which addresses a remote code execution vulnerability; sites should apply this update (and any accompanying Fusion Builder update) immediately.
- If patching cannot be performed immediately: restrict or monitor unauthenticated access to Avada/Fusion Builder front-end endpoints, and review recently created/modified files (particularly PHP files) in the WordPress upload and theme/plugin directories for signs of compromise.
- Review administrator-authored content that could be leveraged as part of the exploitation chain, and audit site file integrity following any suspected exposure.
How IONIX identifies potentially affected assets
IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.
- Raw response body:
fusionJSVars

