CVE-2026-97471

Avada (Fusion) Builder <= 3.16.1 - Unauthenticated Sensitive Information Exposure in 'args[link_target]' Parameter via {user_meta} Dynamic Data Token

2026-10-13 15:10
Luke Eldridge (system)

Strategic Overview

Status
Patched in 3.16.2
Affected Plugin
Avada (Fusion) Builder
Affected Version
<= 3.16.1
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-97471
View all Avada (Fusion) Builder vulnerabilities

At a glance

CVE-2026-97471 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Avada (Fusion) Builder WordPress plugin, affecting versions <= 3.16.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.16.2; sites on affected versions should update now. Disclosed October 2026, reported by Luke Eldridge (system).

Vulnerability Overview

The Avada (Fusion) Builder plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.16.1 via the 'args[link_target]' parameter. This makes it possible for unauthenticated attackers to extract arbitrary user meta values for any user ID, including administrator email addresses, login names, wp_user_level, and WooCommerce customer PII such as billing_email, billing_phone, and billing_address_1. The awb-instagram-nonce required to trigger this endpoint is printed in plaintext in fusionInstagramVars on any page rendering the [fusion_instagram] shortcode, making it harvestable by any anonymous visitor before the exploit request is sent.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Avada (Fusion) Builder <= 3.16.1 carries this weakness at args[link_target], and reaching it takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Avada (Fusion) Builder the fix is 3.16.2: builds <= 3.16.1 are affected, anything from 3.16.2 onward is not.

Remediation

Update to version 3.16.2, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Avada (Fusion) Builder 3.16.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-97471https://www.wordfence.com/threat-intel/vulnerabilities/id/ebbd41a8-b9ff-4afe-bcfd-1df52d8d3b5fhttps://nvd.nist.gov/vuln/detail/CVE-2026-97471

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C