CVE-2025-60248
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 WPClever WPC Product Options for WooCommerce wpc-product-options allows PHP Local File Inclusion.This issue affects WPC Product Options for WooCommerce: from n/a through <= 3.1.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 · high confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the WPC Product Options for WooCommerce plugin (versions <= 3.1.3). The vulnerability allows attackers to include arbitrary local files from the server filesystem through unsanitized user input being used in PHP include/require statements. This can lead to exposure of sensitive configuration files, source code, or other system 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/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.
-
Check installed plugin versionNavigate to WordPress admin dashboard > Plugins > Installed Plugins > WPC Product Options for WooCommerce. The version number is displayed below the plugin name.Affected if The displayed version is 3.1.3 or lower
-
Identify plugin main file locationIn your WordPress installation, locate the plugin directory typically at /wp-content/plugins/wpc-product-options/ and find the main PHP file (often named main.php, plugin.php, or similar).Affected if The plugin is installed and active on the site
-
Check for unsanitized include/require usageExamine the plugin source code for PHP include, include_once, require, or require_once statements that use variables from user input (such as $_GET, $_POST, or $_REQUEST) without proper sanitization.Affected if The code contains include/require statements using unsanitized user-supplied parameters
-
Review access logs for suspicious file inclusion patternsInspect your web server access logs (Apache access.log, Nginx access.log) for requests to the plugin that contain directory traversal sequences like ../ or absolute file paths in query parameters.Affected if Logs show requests with patterns like ?file=../../../../etc/passwd or similar LFI attempts targeting the plugin
-
Check for recent unauthorized file accessReview server logs and file system for any recently accessed configuration files (wp-config.php), sensitive system files, or unexpected file reads that coincide with plugin usage.Affected if Suspicious file access events are logged from the plugin endpoint or associated user sessions
The environment is affected if the WPC Product Options for WooCommerce plugin version is 3.1.3 or lower AND the vulnerable code path accepting user input is accessible on the site.
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 the latest version of WPC Product Options for WooCommerce. If no patch is available, disable the plugin until a fix is released. As a temporary mitigation, restrict web server file permissions and monitor for suspicious file access patterns.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60248 — 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-60248 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