Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-13345: CWE-94 Improper Control of Generation of Code ('Code Injection') in themefusion Avada (Fusion) Builder

0
High
VulnerabilityCVE-2024-13345cvecve-2024-13345cwe-94
Published: Thu Feb 13 2025 (02/13/2025, 06:58:05 UTC)
Source: CVE Database V5
Vendor/Project: themefusion
Product: Avada (Fusion) Builder

Description

CVE-2024-13345 is a high-severity vulnerability in the Avada (Fusion) Builder WordPress plugin that allows unauthenticated attackers to execute arbitrary shortcodes due to improper validation before calling do_shortcode. This code injection flaw affects all versions up to 3. 11. 13 and can lead to partial confidentiality, integrity, and availability impacts. Exploitation requires no authentication or user interaction and can be performed remotely over the network. Although no known exploits are currently reported in the wild, the vulnerability poses a significant risk to websites using this popular builder plugin. Organizations using Avada Builder should prioritize patching or applying mitigations to prevent potential exploitation. Countries with large WordPress user bases and significant Avada plugin adoption are at higher risk. The CVSS 3. 1 base score is 7.

AI-Powered Analysis

AILast updated: 02/26/2026, 01:26:58 UTC

Technical Analysis

CVE-2024-13345 is a code injection vulnerability classified under CWE-94 affecting the Avada (Fusion) Builder plugin for WordPress, versions up to and including 3.11.13. The vulnerability arises because the plugin improperly controls the generation of code by failing to validate inputs before passing them to the WordPress do_shortcode function. This function executes shortcodes, which can embed dynamic content or code within WordPress posts or pages. Due to the lack of validation, unauthenticated attackers can craft requests that execute arbitrary shortcodes, potentially injecting malicious code or commands. The vulnerability is remotely exploitable without any authentication or user interaction, increasing its risk profile. The CVSS 3.1 score of 7.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L) indicates network attack vector, low attack complexity, no privileges or user interaction required, and impacts on confidentiality, integrity, and availability, albeit limited in scope. While no public exploits have been reported yet, the widespread use of Avada Builder in WordPress sites makes this a critical issue to address. The vulnerability could be leveraged to execute malicious payloads, deface websites, steal sensitive data, or disrupt site availability. The absence of official patches at the time of reporting necessitates immediate mitigation steps by administrators.

Potential Impact

The vulnerability allows unauthenticated remote attackers to execute arbitrary shortcodes, which can lead to multiple impacts including partial disclosure of sensitive information (confidentiality), unauthorized modification of site content or behavior (integrity), and potential denial of service or site disruption (availability). Given the popularity of the Avada Builder plugin among WordPress sites globally, exploitation could lead to widespread website defacements, data leakage, or malware distribution. Organizations relying on Avada Builder for their web presence risk reputational damage, loss of customer trust, and potential regulatory consequences if sensitive data is exposed. The ease of exploitation and lack of required privileges make this vulnerability particularly dangerous for public-facing websites. Although no known exploits are currently active, the vulnerability's characteristics make it a likely target for attackers seeking to compromise WordPress sites at scale.

Mitigation Recommendations

1. Immediately update the Avada (Fusion) Builder plugin to a patched version once available from the vendor. 2. Until a patch is released, disable or restrict access to the Avada Builder plugin, especially on public-facing sites. 3. Implement web application firewall (WAF) rules to detect and block suspicious shortcode execution attempts or unusual POST/GET requests targeting the plugin. 4. Restrict shortcode usage to trusted users only and audit shortcode inputs for suspicious content. 5. Harden WordPress installations by limiting plugin permissions and isolating critical components. 6. Monitor web server and application logs for anomalous shortcode execution or unauthorized access patterns. 7. Educate site administrators about the risks of arbitrary shortcode execution and enforce strict input validation policies. 8. Consider deploying runtime application self-protection (RASP) tools that can detect and block code injection attempts in real time. These measures combined will reduce the attack surface and mitigate exploitation risk until official patches are applied.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-01-11T00:56:21.758Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6e51b7ef31ef0b59e252

Added to database: 2/25/2026, 9:49:05 PM

Last enriched: 2/26/2026, 1:26:58 AM

Last updated: 2/26/2026, 6:22:29 AM

Views: 1

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats