CVE-2026-1541: CWE-639 Authorization Bypass Through User-Controlled Key in themefusion Avada (Fusion) Builder
The Avada (Fusion) Builder plugin for WordPress up to version 3. 15. 1 contains a vulnerability that allows authenticated users with Subscriber-level access or higher to access protected post metadata fields. This occurs because the plugin's fusion_get_post_custom_field() function does not properly validate underscore-prefixed metadata keys, which are intended to be protected. The vulnerability can lead to sensitive information exposure via the Dynamic Data feature's post_custom_field parameter. The CVSS score is 4. 3, indicating a medium severity issue. No official patch or remediation guidance is currently available from the vendor. There are no known exploits in the wild at this time.
AI Analysis
Technical Summary
CVE-2026-1541 is a sensitive information exposure vulnerability in the Avada (Fusion) Builder WordPress plugin. The issue arises from the fusion_get_post_custom_field() function failing to validate whether metadata keys are protected (underscore-prefixed). Authenticated users with Subscriber-level privileges or higher can exploit this to retrieve protected post metadata through the Dynamic Data feature's post_custom_field parameter. This vulnerability affects all versions up to and including 3.15.1. The CVSS 3.1 base score is 4.3 (medium severity), reflecting low impact on confidentiality with no impact on integrity or availability. No patch or official remediation is currently documented.
Potential Impact
An attacker with at least Subscriber-level access can access protected post metadata fields that should remain confidential. This leads to sensitive information exposure but does not affect data integrity or availability. The impact is limited to information disclosure within the WordPress environment where the vulnerable plugin is installed.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, limit user roles to trusted individuals only and consider disabling the Dynamic Data feature or restricting its use if possible. Monitor vendor channels for updates and apply patches promptly once available.
CVE-2026-1541: CWE-639 Authorization Bypass Through User-Controlled Key in themefusion Avada (Fusion) Builder
Description
The Avada (Fusion) Builder plugin for WordPress up to version 3. 15. 1 contains a vulnerability that allows authenticated users with Subscriber-level access or higher to access protected post metadata fields. This occurs because the plugin's fusion_get_post_custom_field() function does not properly validate underscore-prefixed metadata keys, which are intended to be protected. The vulnerability can lead to sensitive information exposure via the Dynamic Data feature's post_custom_field parameter. The CVSS score is 4. 3, indicating a medium severity issue. No official patch or remediation guidance is currently available from the vendor. There are no known exploits in the wild at this time.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-1541 is a sensitive information exposure vulnerability in the Avada (Fusion) Builder WordPress plugin. The issue arises from the fusion_get_post_custom_field() function failing to validate whether metadata keys are protected (underscore-prefixed). Authenticated users with Subscriber-level privileges or higher can exploit this to retrieve protected post metadata through the Dynamic Data feature's post_custom_field parameter. This vulnerability affects all versions up to and including 3.15.1. The CVSS 3.1 base score is 4.3 (medium severity), reflecting low impact on confidentiality with no impact on integrity or availability. No patch or official remediation is currently documented.
Potential Impact
An attacker with at least Subscriber-level access can access protected post metadata fields that should remain confidential. This leads to sensitive information exposure but does not affect data integrity or availability. The impact is limited to information disclosure within the WordPress environment where the vulnerable plugin is installed.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, limit user roles to trusted individuals only and consider disabling the Dynamic Data feature or restricting its use if possible. Monitor vendor channels for updates and apply patches promptly once available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-01-28T14:57:30.708Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69deee0b82d89c981fde9f24
Added to database: 4/15/2026, 1:46:51 AM
Last enriched: 4/15/2026, 2:02:03 AM
Last updated: 4/15/2026, 3:00:32 AM
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.