CVE-2025-39364
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 PluginEver Product Category Slider for WooCommerce woo-category-slider-by-pluginever allows PHP Local File Inclusion.This issue affects Product Category Slider for WooCommerce: from n/a through <= 4.3.4.
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 confidenceA PHP Local File Inclusion vulnerability in the PluginEver Product Category Slider for WooCommerce plugin (versions up to 4.3.4) allows attackers to include arbitrary local PHP files due to improper control of filename parameters in include/require statements, potentially leading to remote code execution.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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.
-
Verify the plugin is installedNavigate to WordPress admin > Plugins and look for 'PluginEver Product Category Slider for WooCommerce' in the installed plugins list, or check the /wp-content/plugins/ directory for a folder named 'product-category-slider-for-woocommerce' or similarAffected if The plugin folder exists in the WordPress plugins directory
-
Check the installed plugin versionIn WordPress admin > Plugins, find the plugin and view the version number under the plugin name, or check the main plugin PHP file for the 'Version' header commentAffected if The installed version is 4.3.4 or lower (any version up to and including 4.3.4)
-
Confirm the plugin is activeIn WordPress admin > Plugins, check if the plugin has an 'Active' status rather than 'Inactive'Affected if The plugin is currently activated on the site
-
Identify accessible PHP files handling include/requireExamine the plugin directory for PHP files that contain include, require, include_once, or require_once statements with variables that could be controlled via URL parameters (e.g., parameters like 'file', 'path', 'page', 'slug')Affected if The plugin contains include/require statements where file paths are built from user-supplied input without proper sanitization
-
Test for LFI via HTTP requestsIf the vulnerable endpoint is identified, attempt a controlled test request with a benign file path (e.g., ../../wp-config.php) to see if the application attempts to include it; log the response but do not exploitAffected if The application returns content from or reveals paths to files that should not be accessible via the include/require mechanism
You are affected if the PluginEver Product Category Slider for WooCommerce plugin is installed, active, and running version 4.3.4 or lower, with accessible include/require code paths that accept user-controlled filename parameters.
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 plugin to the latest patched version immediately. If no patch is available, deactivate and remove the plugin until a fix is released. Consider reviewing server file permissions and web root directory access controls as defense-in-depth.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-39364 — 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-39364 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