A chained six-step vulnerability tracked as CVE-2026-18431 makes the Avada theme zero-click RCE a real-world threat: an unauthenticated attacker can execute arbitrary PHP code on any server running a vulnerable version of Avada and its companion Fusion Builder plugin. The flaw carries a 9.8 critical severity score, and because every Avada installation ships with Fusion Builder, the potential target pool maps almost directly to the theme’s entire user base.
Researchers at Wordfence, part of Defiant, published a report on Tuesday setting out the attack chain overview, having deliberately withheld the full technical details to give administrators time to apply patches before exploit code circulates more widely.
How the Avada theme zero-click RCE attack chain works
The exploit is not a single clean bug but a sequence of six weaknesses across authorisation, input validation, trust boundaries, and file handling, each of which must be triggered in a specific order. Wordfence describes the chain as: exposing attacker-controlled input through a public request; passing that input to functionality restricted from anonymous users; invoking a privileged component outside its intended context; using request data to influence trusted state; accessing an insufficiently protected administrative operation; and finally bypassing file-handling restrictions on what can be written and where.
No credentials are required at any step. A successful run gives an attacker arbitrary PHP execution, which in practice means the ability to plant malware, access databases, redirect site visitors to malicious destinations, or create rogue administrator accounts.
CVE-2026-18431 affects Avada versions up to 7.16 and Fusion Builder versions up to 3.16. ThemeFusion, the developer behind both products, released fixes in Avada 7.16.1 and Fusion Builder 3.16.1. According to SocRadar, those patches landed on 25 August 2026. The CVE itself was formally published the following day, on 26 August 2026 at 07:16:45 UTC, as noted by Freshy.
Scope: why every Avada installation is in scope
Avada has recorded more than 1 million sales, which alone makes the vulnerability pool substantial. What removes any ambiguity about the actual exposure is the relationship between the two products. Wordfence clarified to BleepingComputer that ‘Fusion Builder is a required plugin for the Avada theme. Therefore all sites running the Avada theme will also be running the Fusion Builder plugin,’ adding that ‘the prerequisites don’t narrow the pool of potential targets. Any site that has the Avada theme installed is going to be exploitable.’
In other words, the two conditions for exploitation (a vulnerable Avada version and an active Fusion Builder installation) are not independent variables. They are effectively one condition.
Argus: the AI framework that found the chain in two hours
The discovery itself is worth pausing on. Wordfence found and reproduced the six-step chain using an internal agentic framework called Argus, which also generated proof-of-concept exploit code. The whole process took approximately two hours. Argus identified the flaw on 30 July; Wordfence shared the full details with ThemeFusion on 5 August. ThemeFusion acknowledged the report on 10 August and subsequently shipped the fixes on 25 August.
The timeline from discovery to patch is not unusually long by industry standards, but the discovery method adds a layer of urgency: if an agentic framework can chain six weaknesses into working exploit code in under two hours, the window between public disclosure and active exploitation in the wild is likely to be short. Administrators running Avada on production sites should treat updating to 7.16.1, and Fusion Builder to 3.16.1, as an immediate priority rather than a routine maintenance item.
Wordfence has confirmed it is not releasing complete technical details for now, giving the broader WordPress community additional time to patch before the mechanics of the chain become common knowledge. The six-step overview published in the report is enough to understand the attack’s general shape, but not enough to reproduce it without significant additional work.
