Avada forms let unauthenticated attackers invoke any WordPress action, destroying content (CVE-2026-97670)
Avada (Fusion Builder), versions up to and including 7.16.1, contains an authorization bypass that lets unauthenticated visitors invoke arbitrary WordPress action hooks through a form’s dynamic-data token (CVE-2026-97670, CVSS 9.1). Avada is one of the most widely installed WordPress themes, which makes this one land on a lot of doorsteps.
Where a site has a published Avada form with AJAX submission and a notification template that includes form fields (the default form setup), an attacker can send a request that runs core hooks such as wp_scheduled_delete, permanently deleting trashed posts, pages and comments. Other non-denylisted hooks can trigger denial of service or privileged writes through vulnerable third-party code. Researcher Chloe Chamberland reported it through Wordfence’s Argus program.
ThemeFusion released version 7.16.2 with a fix. No active exploitation has been reported, but the attack is simple to automate, needs no login, and works on the default form configuration.
What to do
- Update Avada to 7.16.2 (and Fusion Builder to its matching fixed release) as soon as possible.
- Check your trash and revision history for posts, pages or comments that were deleted without explanation.
- Review recent user registrations and form submissions for anomalies. A web application firewall rule that blocks unexpected action-hook invocations holds the line while you patch.
Page builders sit in the direct path of unauthenticated traffic and run on millions of sites, which is why they keep showing up in this database. ZeroBreach’s recurring scans keep an inventory of every theme and plugin on every app it watches, so a vulnerable builder never goes unnoticed.