CVE-2025-39391
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 zamartz Checkout Field Visibility for WooCommerce checkout-field-visibility-for-woocommerce allows PHP Local File Inclusion.This issue affects Checkout Field Visibility for WooCommerce: from n/a through <= 1.3.0.
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 exists in the zamartz Checkout Field Visibility for WooCommerce plugin (versions <= 1.3.0). The plugin improperly controls filenames used in include/require statements, allowing attackers to manipulate input parameters to include arbitrary local PHP files, 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
- 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.
-
Confirm plugin installationLocate the zamartz Checkout Field Visibility for WooCommerce plugin in the WordPress plugins directory (wp-content/plugins/) or via the WordPress admin plugins listAffected if The plugin folder 'checkout-field-visibility-for-woocommerce' or similar zamartz plugin directory exists on the server
-
Identify installed versionCheck the plugin's main PHP file header for the Version comment, or query the WordPress database wp_options table for the option_name containing the plugin versionAffected if The reported version is 1.3.0 or lower, or if no version is documented (indicating an unpatched older release)
-
Verify plugin is activeCheck the WordPress active_plugins option in wp_options or view the Plugins admin page to confirm the plugin is enabledAffected if The plugin appears in the list of active plugins and is currently enabled on the site
-
Inspect for LFI-vulnerable code patternsExamine the plugin's PHP source files for include(), require(), include_once(), or require_once() statements that use variables or request parameters (e.g., $_GET, $_POST) without proper sanitization or validationAffected if The plugin code contains dynamic file inclusion using unsanitized input parameters that could be manipulated to load arbitrary local PHP files
Your environment is affected if the zamartz Checkout Field Visibility for WooCommerce plugin is installed, active, and running at version 1.3.0 or lower, with vulnerable dynamic file inclusion code present.
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 dataUpgrade to the latest version of Checkout Field Visibility for WooCommerce. If no patch is available, disable the plugin until a secure version is released. Additionally, ensure the web server runs with minimal file system permissions and disable allow_url_include.
- 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-39391 — 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-39391 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