Extensive VC Addons CVE-2025-14475
HIGHAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach admin-ajax.php unauthenticated
-
DeliveryCall extensive_vc_init_shortcode_pagination action
-
ExploitSupply traversal payload in shortcode_name
-
ExecutionBypass weak path normalization
-
PersistInclude attacker-controlled PHP file
-
ImpactExecute arbitrary PHP as web user
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V5 - File Handling File inclusion prevention, allowlisting
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Command and Control The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The Extensive VC Addons for WPBakery plugin (version 1.9.1 or earlier) must be installed and active on the WordPress site, exposing the extensive_vc_init_shortcode_pagination AJAX action to unauthenticated callers via admin-ajax.php. Exploitation is remote and requires no authentication or user interaction (PR:N/UI:N), but full code execution is limited by AC:H: the attacker must supply a shortcode_name value that both defeats the plugin's insufficient path normalization/validation and resolves to an includable PHP file already present or plantable on the server (e.g. an uploaded media file, temp/session file, or poisoned log), since LFI executes existing files rather than injecting new code directly. |
| Impact | This is a genuinely high-priority flaw despite one mitigating metric. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H = 8.1) shows unauthenticated, network-reachable exploitation with full CIA impact, consistent with the CWE-98 file-inclusion-to-RCE classification and the description's claim of 'execution of any PHP code.' The single tempering factor is AC:H, which reflects that turning a Local File Inclusion into reliable code execution requires an includable PHP file to already exist on disk (e.g. an uploaded file, session/log file poisoning, or a bundled PHP path), plus successful bypass of the plugin's partial path normalization - this is not a single-shot, guaranteed win. No EPSS score, KEV listing, or public POC was supplied in the intelligence set, so there is no evidence of active exploitation or automated weaponization at this time; the risk rating rests on the exploitability profile of unauth LFI-to-RCE in WordPress rather than observed attacks. Signals are consistent here (no conflicts between CVSS, CWE, and description), but the AC:H caveat means real-world exploitation is more skilled/targeted than mass-automated until a public exploit emerges. |
| Exploit ScenarioDerived | An unauthenticated attacker sends a crafted request to the WordPress admin-ajax.php endpoint invoking the extensive_vc_init_shortcode_pagination AJAX action with a malicious shortcode_name value using path traversal sequences to point at an attacker-influenced PHP file (such as a previously uploaded file or a poisoned log). The vulnerable extensive_vc_get_module_template_part function includes and executes that file, running arbitrary PHP as the web server user. No public exploit code was identified in the provided data, and AC:H means the attacker must arrange an includable PHP payload and defeat partial path validation. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 30, 2026
Unauthenticated local file inclusion in the Extensive VC Addons for WPBakery page builder plugin affects all versions up to and including 1.9.1, letting remote attackers pass a crafted shortcode_name value to the extensive_vc_init_shortcode_pagination AJAX action so the plugin includes and executes arbitrary PHP files already present on the server. The vulnerability is rated CVSS 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H): exploitation is remote with no authentication or user interaction, but the high attack-complexity metric reflects that the attacker must craft a value that both defeats the plugin's insufficient path normalization and resolves to an includable, attacker-reachable PHP file (for example an uploaded media file, temp/session file, or poisoned log), since LFI executes existing files rather than injecting new code. No public exploit code and no CISA KEV entry were identified at the time of analysis.
RemediationAI
No vendor-released patch was identified in the available data at time of analysis, so the primary action is to deactivate and, if the site does not depend on it, remove the Extensive VC Addons plugin entirely; if the plugin must remain, treat the site as exposed until the vendor publishes a fixed version and track the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/49711408-5d04-4fdd-a6c4-b224959ba1bc?source=cve) plus the Trac trunk sources (https://plugins.trac.wordpress.org/browser/extensive-vc-addon/trunk/lib/helpers-functions.php#L78 and https://plugins.trac.wordpress.org/browser/extensive-vc-addon/trunk/shortcodes/shortcodes-functions.php#L122) for a changed helper, since trunk currently mirrors the vulnerable 1.9.1 code. As compensating controls with their trade-offs: block or filter unauthenticated POSTs to admin-ajax.php where action=extensive_vc_init_shortcode_pagination at the reverse proxy or WAF - effective but easily bypassed by encoding/path variations and it may break legitimate shortcode pagination on public pages; unregister or hook the AJAX action out of wp_ajax_nopriv_extensive_vc_init_shortcode_pagination via a small mu-plugin so the handler is never reached by anonymous callers - this reliably removes the attack path but any front-end pagination feature relying on that action will stop working; and harden include-sink exposure by restricting write access to uploads, disabling file-based session/log paths under the webroot, and applying open_basedir to the WordPress document root - these reduce the pool of includable files an attacker can target but can cause plugin or upload breakage. Regardless of which control is chosen, plan to apply the official plugin update as soon as a patched release above 1.9.1 is available.
Affected ProductsAI
Affected is the Extensive VC Addons for WPBakery page builder WordPress plugin, all versions up to and including 1.9.1; no CPE URI was supplied in the source data, so version pinning must be done by plugin slug and release tag. The vulnerable code resides in the plugin's lib/helpers-functions.php (around line 78, the extensive_vc_get_module_template_part function) and shortcodes/shortcodes-functions.php (lines 122 and 142, the extensive_vc_init_shortcode_pagination AJAX handler), and both the 1.9.1 tag and trunk are cited in the NVD references, so any site running the plugin at 1.9.1 or earlier with the plugin active is exposed. Sites that have the plugin installed but deactivated, or that do not expose admin-ajax.php to untrusted traffic, are not exploitable in this configuration. The vendor/coordinator advisory with the canonical affected-version statement is the Wordfence threat-intel page at https://www.wordfence.com/threat-intel/vulnerabilities/id/49711408-5d04-4fdd-a6c4-b224959ba1bc?source=cve.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The issue is a PHP file-inclusion flaw classed as CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program, 'PHP Remote File Inclusion' family) inside a WordPress plugin that extends the WPBakery page builder. The plugin's helper function extensive_vc_get_module_template_part() (referenced at lib/helpers-functions.php line 78) builds a template path from caller-supplied input, and the shortcode AJAX handler extensive_vc_init_shortcode_pagination (referenced at shortcodes/shortcodes-functions.php lines 122 and 142) feeds the user-controlled shortcode_name parameter into that path-building logic. Because the value is not canonicalized or validated against a whitelist of allowed templates - no realpath() containment check or basename() normalization - traversal sequences and PHP stream wrappers can redirect the include/require to an arbitrary file on disk, which PHP then parses and executes. The attack surface is exposed through WordPress's admin-ajax.php, which is reachable by unauthenticated visitors, so no login is needed. The Wordfence advisory (threat-intel id 49711408-5d04-4fdd-a6c4-b224959ba1bc) is the primary source, and the referenced Trac links point at both the 1.9.1 tag and trunk copies of the vulnerable helper and shortcode files, indicating the sink locations to review when patching.
Know when PHP gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Unauthenticated network AJAX endpoint (AV:N/PR:N/UI:N); AC:H because reliable RCE needs an includable PHP file plus normalization bypass; full CIA once PHP executes.
Primary rating from Vendor (wordfence).
CVSS VectorVendor: wordfence
DescriptionCVE.org
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.
Executive ViewAI
Organizations using the Extensive VC Addons for WPBakery page builder plugin (all versions up to and including 1.9.1) on their WordPress sites are exposed to a high-severity unauthenticated file inclusion vulnerability that could enable remote attackers to execute arbitrary PHP code and compromise the entire website. With no vendor patch currently available, leadership must act to mitigate the risk of data breaches, site defacement, and potential regulatory consequences that could damage customer trust and business operations.
Deploy WAF rules to block exploitation attempts against the extensive_vc_init_shortcode_pagination AJAX action; disable or remove the plugin if not essential; restrict PHP execution in upload directories via server configuration (e.g., .htaccess or nginx rules); enforce strict file upload policies; and monitor logs for suspicious file inclusion activity.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Local File Inclusion vulnerabilities occur when an application accepts user-controlled input to specify which file should be loaded or executed, typically through functions like PHP's `include()`, `require()`, or `fopen()`.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB