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

CVE-2025-60194

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 Premmerce Premmerce Product Search for WooCommerce premmerce-search allows PHP Local File Inclusion.This issue affects Premmerce Product Search for WooCommerce: from n/a through <= 2.2.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 confidence

This is a PHP Local File Inclusion (LFI) vulnerability in the Premmerce Product Search for WooCommerce plugin. The plugin fails to properly validate or sanitize file path parameters before using them in PHP include/require statements, allowing attackers to include arbitrary PHP files from the server's filesystem.

MitigationUpgrade to a patched version of Premmerce Product Search for WooCommerce that properly sanitizes file path inputs in include/require statements. If no patch is available, disable the plugin until a fix is released.

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 Premmerce Product Search for WooCommerce is installed
    Navigate to WordPress admin > Plugins and locate Premmerce Product Search for WooCommerce in the list of active plugins
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed plugin version
    Click on the plugin in the WordPress plugins list to view its details, or check the plugin header in the main PHP file (usually in wp-content/plugins/premmerce-product-search/)
    Affected if The version displayed is any version prior to the patched release
  3. Locate the vulnerable include/require code
    Search the plugin directory for file inclusion patterns that use unsanitized variables, such as 'include($_GET[' or 'require($_POST[' or similar dynamic file paths without sanitization functions
    Affected if Code exists that passes user-supplied input directly to include/require without validation (e.g., include($_GET['file'])
  4. Verify the vulnerable parameter is accessible
    Check if the plugin exposes a frontend or admin URL that accepts a file path parameter (common parameter names: file, path, template, page, include)
    Affected if A publicly accessible parameter accepts file paths without authentication or sanitization

A user is affected if Premmerce Product Search for WooCommerce is installed with any version that contains unsanitized file path parameters in include/require statements and those parameters are accessible.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of Premmerce Product Search for WooCommerce that properly sanitizes file path inputs in include/require statements. If no patch is available, disable the plugin until a fix is released.

Recommended fix Moderate confidence

Version 2.2.5 or later of Premmerce Product Search for WooCommerce

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Premmerce Product Search for WooCommerce'
  4. Check the current installed version number
  5. If the installed version is 2.2.4 or lower, navigate to Plugins > Add New > Upload Plugin
  6. Upload the latest version of Premmerce Product Search for WooCommerce (version 2.2.5 or later)
  7. Activate the updated plugin
  8. Verify the plugin is now running version 2.2.5 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-60194 — 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-60194 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