VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

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

CVE-2026-1541Published · Updated

Action summary

Affected: ≤3.15.1Update to 3.15.2 or newer

All remediation steps
Watch plugin
Severity
Medium4.3
CVSS
4.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:L Privileges required
Low
UI:N User interaction
None
S:U Scope
Unchanged
C:L Confidentiality
Low
I:N Integrity
None
A:N Availability
None
Weakness
CWE-639 Authorization Bypass Through User-Controlled Key
Required access
Unknown
Exploit prediction (EPSS)
No score
CISA KEV
Not listed
On this page8

Am I affected?

Avada (Fusion) Builder fusion-builder

  1. Affected≤ 3.15.1
  2. Patched in3.15.2

Update to 3.15.2 or newer.

You are affected if you run ≤ 3.15.1. Version 3.15.2 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Avada (Fusion) Builder.
  • No admin access? Run a passive check of your site. It reads public files only.

What to do

  1. Update to version 3.15.2, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Avada (Fusion) Builder to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Webbernaut.

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Avada (Fusion) Builder

All 33
More vulnerabilities in Avada (Fusion) Builder
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Form Notification Dynamic-Data action_hook
≤3.16.1Update to 3.16.2
CVE-2026-84938
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting via 'tab_index' and 'empty_notice' Shortcode Attributes
≤3.16.2Update to 3.16.3
CVE-2026-104729
Medium5.3Unauthenticated Sensitive Information Exposure in 'args[link_target]' Parameter via {user_meta} Dynamic Data Token
≤3.16.1Update to 3.16.2
CVE-2026-97471
Critical9.1 Unauthenticated Arbitrary WordPress Action Invocation via '{action_hook}' Dynamic-Data Token in Form Field
≤3.16.1Update to 3.16.2
CVE-2026-97670
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting via 'size' Shortcode Attribute
≤3.15.6Update to 3.16
CVE-2026-16654

Timeline

  1. CVE published

    Severity medium, CVSS 4.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?