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-2025-14475: CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in nenad-obradovic Extensive VC Addons for WPBakery page builder

0
High
VulnerabilityCVE-2025-14475cvecve-2025-14475cwe-98
Published: Sat Dec 13 2025 (12/13/2025, 04:31:24 UTC)
Source: CVE Database V5
Vendor/Project: nenad-obradovic
Product: Extensive VC Addons for WPBakery page builder

Description

The Extensive VC Addons for WPBakery page builder plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.9.1 via the `extensive_vc_get_module_template_part` function. This is due to insufficient path normalization and validation of the user-supplied `shortcode_name` parameter in the `extensive_vc_init_shortcode_pagination` AJAX action. This makes it possible for unauthenticated attackers to include and execute arbitrary PHP files on the server, allowing the execution of any PHP code in those files via the `shortcode_name` parameter.

AI-Powered Analysis

AILast updated: 12/13/2025, 05:00:25 UTC

Technical Analysis

CVE-2025-14475 is a Local File Inclusion vulnerability classified under CWE-98, found in the Extensive VC Addons for WPBakery page builder plugin for WordPress. The flaw exists in the 'extensive_vc_get_module_template_part' function, specifically in the handling of the 'shortcode_name' parameter within the 'extensive_vc_init_shortcode_pagination' AJAX action. Due to insufficient path normalization and validation, attackers can manipulate this parameter to include arbitrary PHP files from the server. This inclusion leads to the execution of any PHP code contained in those files, effectively enabling remote code execution without requiring authentication or user interaction. The vulnerability affects all plugin versions up to and including 1.9.1. The CVSS v3.1 score is 8.1, indicating high severity, with network attack vector, high attack complexity, no privileges required, no user interaction, and full impact on confidentiality, integrity, and availability. While no public exploits are currently known, the vulnerability's nature and the popularity of WPBakery page builder and its addons make it a critical risk for WordPress sites. Attackers could leverage this flaw to compromise web servers, steal sensitive data, deploy malware, or pivot within networks. The lack of available patches at the time of disclosure necessitates immediate mitigation efforts by administrators.

Potential Impact

For European organizations, this vulnerability poses a significant risk to websites and web applications built on WordPress using the Extensive VC Addons for WPBakery page builder plugin. Successful exploitation can lead to full server compromise, data breaches, defacement, or use of the server as a launchpad for further attacks. Given the widespread adoption of WordPress in Europe, including by SMEs, government agencies, and e-commerce platforms, the potential impact includes loss of customer trust, regulatory penalties under GDPR for data breaches, operational disruption, and financial losses. The ability to execute arbitrary PHP code remotely without authentication increases the threat level, especially for organizations lacking robust web application firewalls or monitoring. The vulnerability could also be exploited to deploy ransomware or other malware, amplifying the impact. Organizations relying on this plugin must consider the risk to their web infrastructure and data confidentiality, particularly those handling personal or sensitive information.

Mitigation Recommendations

Immediate mitigation steps include disabling or removing the Extensive VC Addons for WPBakery page builder plugin until a vendor patch is released. Administrators should monitor web server logs for suspicious AJAX requests targeting the 'extensive_vc_init_shortcode_pagination' action with unusual 'shortcode_name' parameters. Implementing a Web Application Firewall (WAF) with custom rules to block requests containing directory traversal patterns or unexpected input in this parameter can reduce exposure. Restricting file permissions on the server to prevent unauthorized PHP file inclusion and execution is critical. Organizations should also ensure their WordPress core, themes, and plugins are regularly updated and conduct security audits focusing on plugin vulnerabilities. If patching is delayed, consider isolating the affected web servers behind reverse proxies or network segmentation to limit attacker access. Backup critical data and verify restoration procedures to mitigate potential damage from exploitation. Finally, educate web administrators about this vulnerability and encourage vigilance for indicators of compromise.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-10T18:24:03.085Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 693cef65d977419e584a50a2

Added to database: 12/13/2025, 4:45:25 AM

Last enriched: 12/13/2025, 5:00:25 AM

Last updated: 12/14/2025, 5:43:22 PM

Views: 16

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats