dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-60204

HIGH · 7.5 CVSS v3.1 Published 2025-11-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Josh Kohlbach WooCommerce Store Toolkit woocommerce-store-toolkit allows PHP Local File Inclusion.This issue affects WooCommerce Store Toolkit: from n/a through <= 2.4.3.

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 confidence

The WooCommerce Store Toolkit plugin versions up to 2.4.3 contain a PHP Local File Inclusion vulnerability due to improper control of filenames in include/require statements. Attackers could potentially include arbitrary local PHP files by manipulating input parameters, leading to code execution or sensitive data exposure.

MitigationUpdate to the latest version of WooCommerce Store Toolkit when available, or implement strict input validation and whitelist-based file inclusion to prevent path traversal attacks.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WooCommerce Store Toolkit is installed
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'WooCommerce Store Toolkit' in the list of active plugins
    Affected if The plugin is installed and active
  2. Identify the installed version
    In the Plugins list, find WooCommerce Store Toolkit and note the version number displayed below the plugin name
    Affected if The version is 2.4.3 or lower (any version up to and including 2.4.3 is affected)
  3. Check for LFI-accessible parameters
    Review the plugin directory for PHP files containing include(), require(), include_once(), or require_once() statements that use unsanitized input from $_GET, $_POST, or $_REQUEST variables as file paths
    Affected if Such vulnerable include/require patterns exist in the plugin code

Your environment is affected if WooCommerce Store Toolkit version 2.4.3 or lower is installed and the plugin contains vulnerable file inclusion code that uses unsanitized user input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of WooCommerce Store Toolkit when available, or implement strict input validation and whitelist-based file inclusion to prevent path traversal attacks.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-60204 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-60204 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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