dbcve.org
Avada BuilderWordPress extension · Theme Fusion

CVE-2024-13345

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-13
Fix available
A fix is available. Upgrade to 3.11.14 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Builder plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 3.11.13. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.

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 Builder WordPress plugin (versions up to 3.11.13) contains an arbitrary shortcode execution vulnerability. The plugin fails to properly validate a user-supplied value before passing it to WordPress's do_shortcode() function, allowing unauthenticated attackers to execute any registered shortcode on the site.

MitigationUpdate Avada Builder to version 3.11.14 or later immediately. Since this is an unauthenticated critical vulnerability (CVSS 9.8), prioritize patching even on production sites and verify shortcode functionality works correctly after the update.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Avada BuilderWordPress extension
Affected:< 3.11.14

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check if Avada Builder plugin is installed
    Log in to WordPress admin and navigate to Plugins > Installed Plugins, or inspect the wp-content/plugins/avada-builder directory via file manager or SSH
    Affected if The plugin is not present in the plugins list or directory
  2. Confirm Avada Builder is active
    In WordPress admin under Plugins > Installed Plugins, verify the Avada Builder plugin shows as 'Active'
    Affected if The plugin is installed but not activated - the vulnerability would not be exploitable in this state
  3. Locate the installed version number
    In WordPress admin, click on the Avada Builder plugin name to view version details, or read the main plugin file (e.g., avada-builder/plugin.php) and look for the 'Version' header in the plugin comment block
    Affected if Unable to determine version - may require filesystem access
  4. Compare version against affected range
    Review the discovered version number against the affected range: versions less than 3.11.14 are vulnerable (e.g., 3.11.13, 3.11.12, 3.11.0, earlier versions)
    Affected if Installed version is 3.11.13 or lower - the plugin is vulnerable to unauthenticated arbitrary shortcode execution

You are affected if Avada Builder plugin is installed, active, and the version is below 3.11.14.

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
Upgrade available Upgrade to 3.11.14 or later
Fixed in 3.11.14
Interim mitigation

Update Avada Builder to version 3.11.14 or later immediately. Since this is an unauthenticated critical vulnerability (CVSS 9.8), prioritize patching even on production sites and verify shortcode functionality works correctly after the update.

Recommended fix High confidence

Avada Builder 3.11.14

  1. Update the Avada Builder plugin to version 3.11.14 or later through the WordPress plugin dashboard, or use 'wp plugin install fusion-builder --update'
  2. Verify the update was successful by checking the plugin version in the WordPress admin dashboard

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

Fix this in Avada Builder 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 the upgrade done

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-2024-13345 — 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-2024-13345 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