dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-1509

MEDIUM · 5.4 CVSS v3.1 Published 2026-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Avada (Fusion) Builder plugin for WordPress is vulnerable to Arbitrary WordPress Action Execution in all versions up to, and including, 3.15.1. This is due to the plugin's `output_action_hook()` function accepting user-controlled input to trigger any registered WordPress action hook without proper authorization checks. This makes it possible for authenticated attackers, with Subscriber-level access and above, to execute arbitrary WordPress action hooks via the Dynamic Data feature, potentially leading to privilege escalation, file inclusion, denial of service, or other security impacts depending on which action hooks are available in the WordPress installation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Avada (Fusion) Builder plugin for WordPress versions up to 3.15.1 contains an arbitrary action execution vulnerability in the output_action_hook() function. Authenticated attackers with Subscriber-level access can inject arbitrary WordPress action hook names via the Dynamic Data feature, triggering any registered WordPress action without authorization. This enables privilege escalation, potential file inclusion, or DoS depending on available hooks.

MitigationUpdate Avada (Fusion) Builder to version 3.15.2 or later which adds proper authorization checks to the output_action_hook() function.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Avada (Fusion) Builder is installed
    Navigate to WordPress dashboard > Plugins and confirm 'Avada' or 'Fusion Builder' appears in the installed plugins list with status 'Active'
    Affected if Avada or Fusion Builder plugin is installed and active in WordPress
  2. Check installed Avada version
    Go to Plugins > Installed Plugins > click 'View details' on Avada or check the plugin header comment in /wp-content/plugins/fusion-builder/fusion-builder.php for the version number
    Affected if Version is 3.15.1 or lower (any version up to and including 3.15.1)
  3. Confirm Dynamic Data feature exists
    Access the Fusion Builder editor interface (found in page/post edit screens) and verify the Dynamic Data option is present and accessible in the builder options
    Affected if Dynamic Data feature is available and can be accessed by users with Subscriber-level permissions
  4. Inspect for unauthorized action hooks
    Review WordPress audit logs, server access logs, or database for suspicious entries involving 'do_action', 'wp_ajax_fusion_builder_output_action', or custom action hook names in POST requests to /wp-admin/admin-ajax.php
    Affected if Any unexpected or unauthorized action hook executions are logged or present in audit data

A user is affected if Avada (Fusion) Builder version 3.15.1 or lower is installed, the Dynamic Data feature is accessible, and no additional access controls beyond authentication are enforced.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Avada (Fusion) Builder to version 3.15.2 or later which adds proper authorization checks to the output_action_hook() function.

Recommended fix Moderate confidence

Latest Avada (Fusion) Builder version (likely 3.15.2 or higher)

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the Avada (Fusion) Builder plugin
  4. 4. Check if an update is available and update to the latest version
  5. 5. Verify the update was successful by checking the plugin version
  6. 6. Test that the Dynamic Data feature still functions correctly
  7. 7. Confirm that unauthorized users cannot trigger arbitrary action hooks
Caveat Minor version updates typically have low risk; review Avada's changelog for any breaking changes before upgrading in complex setups

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1509 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1509 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data