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

CVE-2025-60192

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 Wholesale Pricing for WooCommerce premmerce-woocommerce-wholesale-pricing allows PHP Local File Inclusion.This issue affects Premmerce Wholesale Pricing for WooCommerce: from n/a through <= 1.1.10.

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

A Local File Inclusion (LFI) vulnerability exists in the Premmerce Wholesale Pricing for WooCommerce WordPress plugin. The vulnerability stems from improper control of filenames used in PHP include/require statements, allowing attackers to potentially include arbitrary local PHP files by manipulating input parameters.

MitigationUpdate the plugin to the latest patched version once released, or implement strict input validation and whitelist-based file inclusion logic to prevent path traversal and unauthorized file inclusion.

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. Identify if the Premmerce Wholesale Pricing for WooCommerce plugin is installed
    Navigate to WordPress admin > Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'premmerce-wholesale-pricing' or similar Premmerce-related directories
    Affected if The plugin directory exists on the WordPress installation
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and look for the version number displayed for Premmerce Wholesale Pricing for WooCommerce; alternatively, check the main plugin PHP file for a 'Version' header comment
    Affected if The installed version matches any version known to contain this LFI vulnerability (compare against the vendor's release notes for the patched version)
  3. Inspect web server access logs for file inclusion attempts
    Review HTTP access logs (typically in /var/log/apache2/, /var/log/nginx/, or similar) for requests containing '../' path traversal sequences or direct file paths sent to plugin endpoints
    Affected if Suspicious requests with path traversal patterns targeting the plugin are found in the logs
  4. Check for unauthorized PHP file modifications
    Compare the plugin's current file hashes or modification timestamps against a known clean backup, or inspect key PHP files for suspicious code injections (particularly files with include/require statements)
    Affected if Plugin files have been modified from their original state or contain unexpected code
  5. Verify user input handling in plugin configuration
    If accessible, examine the plugin's admin settings or any frontend forms that accept file paths or parameters, looking for direct use of user input in include/require statements without sanitization
    Affected if The plugin accepts file path parameters without proper validation or whitelisting

A user is affected if they have the Premmerce Wholesale Pricing for WooCommerce plugin installed and running a version that contains the LFI vulnerability, particularly if the plugin processes user-supplied file path parameters.

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 the plugin to the latest patched version once released, or implement strict input validation and whitelist-based file inclusion logic to prevent path traversal and unauthorized file inclusion.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

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