CVE-2025-39378
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 Holest Engineering Spreadsheet Price Changer for WooCommerce and WP E-commerce – Light excel-like-price-change-for-woocommerce-and-wp-e-commerce-light allows PHP Local File Inclusion.This issue affects Spreadsheet Price Changer for WooCommerce and WP E-commerce – Light: from n/a through <= 2.4.37.
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 confidenceLocal File Inclusion vulnerability in the Holest Engineering Spreadsheet Price Changer plugin allows attackers to include arbitrary local PHP files via unsanitized input in include/require statements. This can lead to remote code execution if attackers can upload files or access sensitive system files.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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.
-
Locate the Holest Engineering Spreadsheet Price Changer plugin installationSearch your web server file system for the plugin directory, typically found under /wp-content/plugins/ with names containing 'spreadsheet-price-changer', 'holest', or similar variations. Check your CMS plugin management interface if this is a WordPress site.Affected if The plugin directory exists on the server and is actively installed.
-
Identify the installed plugin versionCheck the main plugin PHP file for a version constant or comment, typically found in the primary plugin file (often named plugin-name.php or index.php inside the plugin folder). Common locations include a 'Version:' header in the file comments or a defined VERSION constant.Affected if The detected version is any version of this plugin, as no fixed version was specified in the advisory.
-
Verify the vulnerable include/require code paths existSearch the plugin source code for include, include_once, require, or require_once statements that use variables or user-supplied input without proper sanitization. Look for patterns like 'include($var)', 'include($_GET[...])', or 'require($path)' without validation functions such as realpath(), basename(), or whitelist checks.Affected if Unsanitized include/require statements are found that accept external input directly.
-
Check if the vulnerable endpoints are publicly accessibleReview your web server access logs or test direct HTTP access to suspected vulnerable scripts within the plugin directory. Determine if the affected PHP files can be invoked without authentication or are accessible to unauthenticated users.Affected if The vulnerable code paths can be triggered by unauthenticated users via HTTP requests.
-
Assess file upload or write capabilitiesExamine the plugin for any file upload functionality, temporary file creation, or write access to directories accessible via the web server. Check for upload forms, import features, or any code that writes files to the web document root or accessible directories.Affected if The plugin or server configuration allows file uploads or writable directories accessible to the attacker, enabling RCE via LFI.
You are affected if the Holest Engineering Spreadsheet Price Changer plugin is installed and its vulnerable include/require code paths are accessible without proper input validation.
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 to the latest version of the plugin when available. Until then, disable the plugin or restrict access to affected endpoints via web server configuration. Review code for proper input validation on all include/require statements.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-39378 — 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-39378 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