Vulnerability in Extensive VC Addons for WPBakery page builder (WordPress plugin) (CVE-2025-14475)
Summary
Vulnerability in Extensive VC Addons for WPBakery page builder (WordPress plugin) (CVE-2025-14475). Successful exploitation can lead to full system takeover. Exploitable via extensive_vc_get_module_template_part.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-14475 has been found in Extensive VC Addons for WPBakery page builder (WordPress plugin).
Attackers can target a specific entry point like extensive_vc_get_module_template_part over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Extensive VC Addons for WPBakery page builder (WordPress plugin) CVE-2025-14475" on the vendor's site.
CVE-2025-14475 (Extensive VC Addons for WPBakery page builder (WordPress plugin)) — CWE-98 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: extensive_vc_get_module_template_part / shortcode_name / extensive_vc_init_shortcode_pagination
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-98) exists in Extensive VC Addons for WPBakery page builder (WordPress plugin). Attackers reach the vulnerable code path via extensive_vc_get_module_template_part without authentication.
Check the vendor advisory for the affected versions of Extensive VC Addons for WPBakery page builder (WordPress plugin). Attack surface: extensive_vc_get_module_template_part / shortcode_name / extensive_vc_init_shortcode_pagination.
Severity: High (CVSS 8.1/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Extensive VC Addons for WPBakery page builder (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。