Skip to main content
Mallory
MediumVulnerability

CVE-2026-1541: Sensitive Information Exposure in Avada Builder Dynamic Data post_custom_field

Published Apr 15, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.3Medium · v3.1
EPSS0.29%21st percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
IdentifiersCVE-2026-1541CWE-200

CVE-2026-1541 is a sensitive information exposure vulnerability in the Avada (Fusion) Builder plugin for WordPress affecting all versions through 3.15.1. The issue is caused by the plugin's fusion_get_post_custom_field() function not validating whether requested metadata keys are protected, specifically underscore-prefixed post meta fields that are intended to remain non-public. Through the Dynamic Data feature's post_custom_field parameter, an authenticated user can retrieve protected post metadata that should not be exposed to lower-privileged users.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an authenticated attacker with Subscriber-level privileges or higher to read protected post metadata that is normally not intended to be accessible through the plugin's Dynamic Data functionality. Depending on what is stored in protected post meta, this may expose sensitive configuration values, internal content metadata, workflow-related data, or other non-public information associated with WordPress posts.

Mitigation

If you can’t patch tonight, do this now.

Until a patched version is deployed, restrict access to accounts with Subscriber-level or higher privileges, minimize assignment of low-privilege authenticated accounts, and review whether the Dynamic Data feature can be disabled or its use constrained in environments where untrusted users have access. Audit protected post metadata for sensitive values and reduce storage of secrets or security-relevant data in post meta where possible.

Remediation

Patch, then assume compromise.

Update the Avada (Fusion) Builder plugin to a version newer than 3.15.1 once a vendor-fixed release is available. The underlying flaw should be corrected by enforcing validation that blocks access to protected underscore-prefixed metadata keys in fusion_get_post_custom_field() and any equivalent Dynamic Data retrieval paths.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-1541 exploited in the wild?
Yes. As of Sep 25, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2026-1541?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-1541.
Is there a patch for CVE-2026-1541?
Update the Avada (Fusion) Builder plugin to a version newer than 3.15.1 once a vendor-fixed release is available. The underlying flaw should be corrected by enforcing validation that blocks access to protected underscore-prefixed metadata keys in fusion_get_post_custom_field() and any equivalent Dynamic Data retrieval paths.
How severe is CVE-2026-1541?
CVE-2026-1541 has a CVSS v3.1 score of 4.3 (Medium) and an EPSS score of 0.29% (21st percentile) as of Sep 25, 2026.
Activity feed

Recent activity

5 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity4Community discussion across Reddit, Mastodon, and other social sources.