Avada (Fusion) Builder (<= 7.16.1) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/avada-fusion-builder--7.16.1/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioSat, 10 Oct 2026 05:34:20 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgCVE-2026-97670 Authorization Bypass in Avada Fusion Builderhttps://feed.craftedsignal.io/briefs/2026-10-avada-builder-auth-bypass/Sat, 10 Oct 2026 05:34:20 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-avada-builder-auth-bypass/An unauthenticated authorization bypass in the Avada Fusion Builder plugin for WordPress allows attackers to trigger arbitrary action hooks via crafted AJAX form submissions.The Avada Fusion Builder plugin for WordPress is vulnerable to an authorization bypass flaw (CVE-2026-97670) affecting all versions up to and including 7.16.1. The issue stems from the plugin's failure to verify authorization before dispatching WordPress action hooks parsed from attacker-supplied form data. Specifically, the plugin's dynamic-data token system handles the {action_hook,...} token within form notification email templates without adequate validation. Because the plugin's internal trust gate only inspects 'args' parameters and ignores 'formData' processed during AJAX submissions, an unauthenticated attacker can supply arbitrary hooks. When an Avada form with a notification template is submitted, the plugin executes these hooks, leading to unauthorized state changes. This can result in permanent site content deletion, denial of service, or the invocation of vulnerable third-party handlers. The vulnerability also facilitates a blind arbitrary meta-read, although exfiltration is limited by the plugin's response path.

Attack Chain

  1. Attacker identifies a WordPress site running a vulnerable version of Avada Fusion Builder.
  2. Attacker locates a page containing a published Avada form with AJAX submission enabled.
  3. Attacker crafts a POST request to the plugin's public form-submit endpoint containing malicious form data.
  4. Attacker inserts a dynamic-data token, such as {action_hook,wp_scheduled_delete}, into the 'formData' parameters.
  5. The plugin parses the 'formData', bypasses the incomplete 'is_content_request_supplied' security check, and fails to validate the hook name.
  6. The plugin dispatches the requested WordPress action hook, executing the core function (e.g., permanent deletion of trashed posts).
  7. Final objective: unauthorized site state modification, site content destruction, or service disruption.

Impact

Successful exploitation allows unauthenticated attackers to trigger sensitive WordPress core and plugin-specific action hooks. This leads to the permanent, irreversible destruction of site content including posts, pages, and comments, as well as potential denial of service through auto-update hooks. While the vulnerability also allows for arbitrary meta-reading, observed exploitation vectors center on unauthorized administrative state changes and data loss.

Recommendation

  1. Immediately update the Avada Fusion Builder plugin to a version released after 7.16.1 to resolve CVE-2026-97670.
  2. Monitor web server logs for suspicious POST requests to form submission endpoints that include patterns such as '{action_hook' or common WordPress administrative hooks.
  3. Audit Avada form configurations to identify and sanitize active notification email templates that use dynamic-data tokens.
]]>highthreatwordpressplugin-vulnerabilitycve-2026-97670