CVE-2025-31405
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 zankover Fami WooCommerce Compare fami-woocommerce-compare allows PHP Local File Inclusion.This issue affects Fami WooCommerce Compare: from n/a through <= 1.0.5.
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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the Fami WooCommerce Compare WordPress plugin. The vulnerability stems from improper control of filename parameters in include/require statements, allowing attackers to include arbitrary local PHP files. This can lead to remote code execution if an attacker can control the included file path.
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.
-
Identify if Fami WooCommerce Compare plugin is installedAccess WordPress admin dashboard under Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'fam-woocommerce-compare' or similarAffected if The plugin folder exists in the WordPress plugins directory
-
Check installed plugin versionIn WordPress admin, view plugin details to see the version number, or open the main plugin PHP file (usually contains version definition in header comments)Affected if Unable to determine version or version is older than any patched release (no patch version specified in CVE)
-
Locate vulnerable PHP files in plugin directorySearch the plugin folder for PHP files containing include, require, include_once, or require_once statements that use variables in the file path (e.g., include($file); require($_GET['file']);)Affected if Any PHP file in the plugin uses dynamic file inclusion without proper sanitization of input parameters
-
Verify web-accessible plugin filesCheck if plugin PHP files with dynamic include statements are accessible via HTTP requests (e.g., attempt to access suspected vulnerable files directly)Affected if Vulnerable include/require patterns exist and are reachable via web requests without authentication
-
Monitor for exploitation indicators in access logsReview web server access logs (Apache/nginx) for requests to the plugin containing ../ directory traversal sequences or suspicious file parameters
Your environment is affected if the Fami WooCommerce Compare plugin is installed and contains dynamic include/require statements using unsanitized variables, making local file inclusion possible.
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 a patched version of Fami WooCommerce Compare (if available). If no patch exists, disable the plugin immediately. As a temporary workaround, ensure the web server runs with minimal file permissions and disable allow_url_include.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31405 — 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-31405 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