dbcve.org
AvadaWordPress extension · Theme Fusion

CVE-2024-13346

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-13
Fix available
A fix is available. Upgrade to 7.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 | Website Builder For WordPress & WooCommerce theme for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 7.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 WordPress theme fails to validate user input before passing it to PHP's do_shortcode() function, allowing unauthenticated attackers to execute arbitrary shortcodes. This can lead to remote code execution depending on available shortcodes.

MitigationUpdate the Avada theme to version 7.11.14 or later to patch the vulnerability. Until patched, monitor for suspicious requests to endpoints using shortcode parameters.

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
AvadaWordPress extension
Affected:< 7.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. Verify Avada theme installation
    Check for the Avada theme directory in your WordPress installation at wp-content/themes/avada/ or list installed themes via WordPress admin under Appearance > Themes
    Affected if Avada theme is present in the WordPress installation
  2. Determine installed Avada version
    Open wp-content/themes/avada/style.css and read the 'Version:' declaration in the file header, or check the theme version displayed in WordPress admin under Appearance > Themes
    Affected if The version number found is lower than 7.11.14 (for example, 7.11.13, 7.11.0, 7.10.0, etc.)
  3. Inspect HTTP access logs for shortcode-related requests
    Search your web server access logs (Apache access_log, Nginx access.log) for patterns like 'shortcode', 'do_shortcode', or common shortcode parameters in query strings (e.g., ?shortcode=, ?sc=, or parameters containing 'shortcode' in the URL)
    Affected if Unauthenticated requests contain shortcode parameters being passed to the site, indicating potential exploitation attempts or probing
  4. Identify exposed shortcode-handling endpoints
    Review PHP code in the Avada theme for any public-facing files that process shortcode parameters from GET or POST requests, particularly files in the theme root or includes/ directory that call do_shortcode() on user-supplied input
    Affected if The theme exposes an endpoint where user input is directly passed to do_shortcode() without sanitization and is accessible without authentication

A user is affected if the Avada theme version is installed and is lower than 7.11.14, and the vulnerable shortcode-handling functionality is accessible to unauthenticated users.

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 7.11.14 or later
Fixed in 7.11.14
Interim mitigation

Update the Avada theme to version 7.11.14 or later to patch the vulnerability. Until patched, monitor for suspicious requests to endpoints using shortcode parameters.

Recommended fix High confidence

Avada 7.11.14

  1. Log in to the WordPress admin dashboard
  2. Navigate to Appearance > Themes
  3. If there is an update notification for Avada, click on the 'Update Now' button to update to the latest version
  4. Alternatively, navigate to Avada > Theme Options > Advanced > Updates and check for updates
  5. Ensure the updated version is 7.11.14 or later
  6. After updating, verify the site functionality remains intact
  7. Consider backing up the site before performing any updates
Caveat Major theme updates may affect existing layouts or customizations; test in staging environment first

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

Fix this in Avada Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13346 — 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-13346 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