CVE-2025-60191
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 Premmerce Premmerce Wishlist for WooCommerce premmerce-woocommerce-wishlist allows PHP Local File Inclusion.This issue affects Premmerce Wishlist 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 · moderate confidenceThis is a PHP Local File Inclusion vulnerability in the Premmerce Wishlist for WooCommerce plugin. The improper control of filename for include/require statements allows attackers to manipulate file paths and potentially execute arbitrary PHP code by including malicious local files.
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.
-
Verify Premmerce Wishlist plugin is installedLocate the plugin directory in the WordPress installation (typically wp-content/plugins/). Search for directories containing 'premmerce' and 'wishlist' in the name. Check the main plugin file for the plugin header which contains the version number.Affected if The plugin directory exists and contains premmerce wishlist files.
-
Identify the installed plugin versionOpen the main plugin PHP file (usually named premmerce-wishlist.php or similar). Look for the plugin header comment block which contains 'Version: x.x.x' or check the readme.txt file for the 'Stable tag' entry.Affected if The version displayed cannot be compared to a patched version because no specific vulnerable version range was provided.
-
Examine the plugin for file inclusion functions using user inputSearch the plugin source code for PHP include, include_once, require, or require_once statements. Check if any of these use parameters that could originate from user request data such as $_GET, $_POST, or $_REQUEST without proper sanitization using basename() or realpath().Affected if The code contains include/require statements that use unsanitized user-controlled path parameters.
-
Test if the vulnerable parameter is externally accessibleIdentify the HTTP parameter name used in the potentially vulnerable include/require code. Attempt a controlled test request (using a safe test file) to see if the parameter allows path traversal (e.g., ../../) to include files outside the plugin directory.Affected if The parameter accepts path traversal sequences and returns content from arbitrary local files.
You are affected if the Premmerce Wishlist for WooCommerce plugin is installed and its code contains include/require statements using unsanitized user-supplied path parameters that can be exploited for local file inclusion.
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 dataUpdate the plugin to the latest version if a patched release is available. If no patch exists, disable or remove the plugin. Implement strict input validation and use basename() functions on any user-controlled file path parameters to prevent path traversal attacks.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60191 — 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-60191 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