CVE-2025-60087
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Nenad Obradovic Extensive VC Addons for WPBakery page builder extensive-vc-addon allows PHP Local File Inclusion.This issue affects Extensive VC Addons for WPBakery page builder: from n/a through <= 1.9.1.
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 · moderate confidenceA Local File Inclusion (LFI) vulnerability exists in the Extensive VC Addons for WPBakery page builder WordPress plugin (versions up to 1.9.1). The vulnerability stems from improper control of filenames in PHP include/require statements, allowing attackers to potentially include and execute arbitrary PHP files from the server.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Extensive VC Addons plugin is installedAccess WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'Extensive VC Addons' or 'Extensive VC' in the list of active pluginsAffected if The plugin appears in the installed plugins list
-
Identify the installed version of Extensive VC AddonsIn the WordPress admin under Plugins > Installed Plugins, click on the plugin to view its details, or check the plugin header in /wp-content/plugins/extensive-vc-addons/ directory for the Version fieldAffected if The displayed version matches or falls within an affected version range (compare to known vulnerable versions)
-
Verify WPBakery page builder is activeCheck if WPBakery Page Builder (also called Visual Composer) is installed and active on the WordPress site, as this is a required component for the vulnerable pluginAffected if WPBakery Page Builder is installed and running alongside Extensive VC Addons
-
Inspect plugin files for include/require statements with dynamic inputExamine PHP files in the plugin directory, specifically looking for include(), require(), include_once(), or require_once() functions that use variables or request parameters as file pathsAffected if Dynamic file inclusion using user-controlled input is found in the plugin code
-
Review access logs for directory traversal patternsCheck web server access logs (Apache error.log, Nginx access.log) or WordPress debug logs for requests containing ../ patterns or direct file path manipulation targeting the pluginAffected if Suspicious requests with ../ sequences or unusual file path parameters targeting the plugin are present in logs
A user is affected if the Extensive VC Addons plugin is installed, WPBakery Page Builder is present, and the plugin contains dynamic file inclusion code vulnerable to path manipulation.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the Extensive VC Addons plugin to the latest version if available, or remove/disable the plugin until a patch is released. If the plugin cannot be updated, disable it and assess for signs of compromise.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60087 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-60087 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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