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-13592: CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in labibahmed42 Team Builder For WPBakery Page Builder(Formerly Visual Composer)

0
High
VulnerabilityCVE-2024-13592cvecve-2024-13592cwe-98
Published: Wed Feb 19 2025 (02/19/2025, 07:32:14 UTC)
Source: CVE Database V5
Vendor/Project: labibahmed42
Product: Team Builder For WPBakery Page Builder(Formerly Visual Composer)

Description

CVE-2024-13592 is a high-severity Local File Inclusion (LFI) vulnerability in the Team Builder For WPBakery Page Builder WordPress plugin, affecting all versions up to 1. 0. Authenticated users with Contributor-level access or higher can exploit this flaw via the 'team-builder-vc' shortcode to include and execute arbitrary files on the server. This allows attackers to run arbitrary PHP code, potentially bypassing access controls and accessing sensitive data. The vulnerability arises from improper control of filenames used in include/require statements (CWE-98). Exploitation does not require user interaction but does require low-level authenticated access. No public exploits are known yet, but the impact includes full confidentiality, integrity, and availability compromise of affected systems. Organizations using this plugin should prioritize patching or mitigating this vulnerability immediately.

AI-Powered Analysis

AILast updated: 02/25/2026, 23:26:12 UTC

Technical Analysis

CVE-2024-13592 is a Local File Inclusion vulnerability classified under CWE-98, found in the Team Builder For WPBakery Page Builder plugin for WordPress, formerly known as Visual Composer. The vulnerability exists in all versions up to and including 1.0 and is triggered via the 'team-builder-vc' shortcode. It allows authenticated users with Contributor-level permissions or higher to manipulate the filename parameter used in PHP include or require statements improperly. This flaw enables attackers to include arbitrary files from the server, which can contain malicious PHP code. Since WordPress contributors can upload files such as images, attackers may upload files with embedded PHP code disguised as safe file types and then include them to execute arbitrary code. This can lead to full system compromise, including bypassing access controls, data exfiltration, and remote code execution. The vulnerability has a CVSS v3.1 base score of 7.5, reflecting high severity, with network attack vector, low privileges required, no user interaction, and high impact on confidentiality, integrity, and availability. Although no known exploits are currently in the wild, the vulnerability presents a significant risk due to the widespread use of the affected plugin and the ease of exploitation once authenticated access is obtained.

Potential Impact

The impact of CVE-2024-13592 is severe for organizations using the affected WordPress plugin. An attacker with Contributor-level access can execute arbitrary PHP code on the server, potentially leading to full system compromise. This includes bypassing WordPress access controls, stealing sensitive data such as user credentials and database contents, defacing websites, deploying malware or ransomware, and disrupting service availability. Since WordPress powers a large portion of websites globally, including many business and e-commerce sites, exploitation could result in significant reputational damage, financial loss, and regulatory penalties. The requirement for authenticated access limits exposure somewhat but does not eliminate risk, as Contributor accounts are commonly available in multi-user environments or can be compromised through phishing or other means. The ability to upload seemingly safe files that can be included and executed increases the attack surface and complicates detection and prevention.

Mitigation Recommendations

To mitigate CVE-2024-13592, organizations should immediately update the Team Builder For WPBakery Page Builder plugin to a patched version once available. In the absence of an official patch, administrators should restrict Contributor-level permissions to trusted users only and audit existing Contributor accounts for suspicious activity. Implement strict file upload validation and sanitization to prevent uploading files containing executable code disguised as images or other safe types. Disable or restrict the use of the vulnerable 'team-builder-vc' shortcode if possible. Employ Web Application Firewalls (WAFs) with rules to detect and block attempts to exploit LFI vulnerabilities. Monitor server logs for unusual file inclusion attempts and anomalous PHP execution patterns. Additionally, consider isolating the WordPress environment using containerization or sandboxing to limit the impact of potential code execution. Regularly back up website data and configurations to enable recovery in case of compromise.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-01-21T15:07:03.682Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6e61b7ef31ef0b59f4bc

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

Last enriched: 2/25/2026, 11:26:12 PM

Last updated: 2/26/2026, 6:17:20 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