dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-14475

HIGH · 8.1 CVSS v3.1 Published 2025-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Extensive VC Addons plugin for WPBakery (versions up to 1.9.1) contains an unauthenticated Local File Inclusion vulnerability in the AJAX action `extensive_vc_init_shortcode_pagination`. The `shortcode_name` parameter is not properly validated or path-normalized, allowing attackers to use path traversal sequences to include and execute arbitrary PHP files on the server, achieving remote code execution.

MitigationUpdate the Extensive VC Addons plugin to the latest version immediately. If no patched version is available, remove the plugin entirely or disable the affected AJAX endpoint via .htaccess or server configuration to block unauthenticated requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Extensive VC Addons plugin
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'extensive-vc-addons' or similar. Also check the WordPress admin under Plugins > Installed Plugins.
    Affected if The plugin folder exists in the WordPress installation.
  2. Determine the installed version
    Open the main plugin PHP file (typically extensive-vc-addons.php) and look for the version header comment at the top, or check the plugin's readme.txt file. Alternatively, query the wp_options table in the database for the option_name containing 'extensive_vc' and 'version'.
    Affected if The version is 1.9.1 or lower, or the version cannot be determined but the plugin is present.
  3. Verify the vulnerable AJAX endpoint is active
    Send a request to your WordPress site's /wp-admin/admin-ajax.php with parameters action=extensive_vc_init_shortcode_pagination&shortcode_name=test. Check if the server returns a response rather than a 404 or auth error.
    Affected if The endpoint responds to unauthenticated requests, indicating the AJAX action is registered and accessible.
  4. Inspect the vulnerable code
    In the plugin directory, search for the function handling 'extensive_vc_init_shortcode_pagination' or the 'shortcode_name' parameter. Look for include(), require(), or similar file-loading functions that use this parameter without sanitization.
    Affected if The code uses the shortcode_name parameter in include/require statements without proper path validation or path traversal prevention.

You are affected if the Extensive VC Addons plugin is installed with version 1.9.1 or lower, the AJAX endpoint is accessible without authentication, and the vulnerable code pattern is present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Extensive VC Addons plugin to the latest version immediately. If no patched version is available, remove the plugin entirely or disable the affected AJAX endpoint via .htaccess or server configuration to block unauthenticated requests.

Recommended fix Moderate confidence

Version 1.9.2 or latest available version

  1. 1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
  2. 2. Locate 'Extensive VC Addons for WPBakery page builder' in the plugin list
  3. 3. Check if an update is available for this plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is running version 1.9.2 or higher
  6. 6. Test that the shortcode functionality still works correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14475 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14475 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data