CVE-2026-1541

Avada (Fusion) Builder <= 3.15.1 - Authenticated (Subscriber+) Sensitive Information Exposure via Insecure Direct Object Reference

2026-04-14 12:23
Webbernaut

Strategic Overview

Status
Patched in 3.15.2
Affected Plugin
Avada (Fusion) Builder
Affected Version
<= 3.15.1
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-1541
View all Avada (Fusion) Builder vulnerabilities

At a glance

CVE-2026-1541 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Avada (Fusion) Builder WordPress plugin, affecting versions <= 3.15.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.15.2; sites on affected versions should update now. Disclosed April 2026, reported by Webbernaut.

Vulnerability Overview

The Avada (Fusion) Builder plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.15.1. This is due to the plugin's `fusion_get_post_custom_field()` function failing to validate whether metadata keys are protected (underscore-prefixed). This makes it possible for authenticated attackers, with Subscriber-level access and above, to extract protected post metadata fields that should not be publicly accessible via the Dynamic Data feature's `post_custom_field` parameter.

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 interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Avada (Fusion) Builder <= 3.15.1 carries this weakness at fusion_get_post_custom_field(), and reaching it takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Avada (Fusion) Builder the fix is 3.15.2: builds <= 3.15.1 are affected, anything from 3.15.2 onward is not.

Remediation

Update to version 3.15.2, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Avada (Fusion) Builder 3.15.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-1541https://www.wordfence.com/threat-intel/vulnerabilities/id/f1f69f93-80e3-434d-98a6-fc8757b4e6d1https://nvd.nist.gov/vuln/detail/CVE-2026-1541

Related records

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