CVE-2026-1541
Received Received - Intake
Sensitive Data Exposure in Avada Builder Plugin Metadata Access

Publication date: 2026-04-15

Last updated on: 2026-04-15

Assigner: Wordfence

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-15
Last Modified
2026-04-15
Generated
2026-05-06
AI Q&A
2026-04-15
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
fusion_builder avada_builder to 3.15.1 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The Avada (Fusion) Builder plugin for WordPress has a vulnerability in versions up to and including 3.15.1. The issue arises because the plugin's function `fusion_get_post_custom_field()` does not properly check if metadata keys are protected (those starting with an underscore). As a result, authenticated users with Subscriber-level access or higher can access protected post metadata fields that should normally be hidden, using the Dynamic Data feature's `post_custom_field` parameter.


How can this vulnerability impact me? :

This vulnerability allows attackers with low-level authenticated access to extract sensitive or protected metadata from posts that should not be publicly accessible. This could lead to exposure of confidential or private information stored in these metadata fields, potentially compromising the privacy or security of the website's content or users.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

This vulnerability allows authenticated users with Subscriber-level access and above to extract protected post metadata fields that should not be publicly accessible. Such unauthorized exposure of sensitive information could potentially lead to non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive data from unauthorized access.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart