CVE-2025-60203
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 Josh Kohlbach Store Exporter woocommerce-exporter allows PHP Local File Inclusion.This issue affects Store Exporter: from n/a through <= 2.7.6.
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 confidenceLocal File Inclusion (LFI) vulnerability in the WooCommerce Store Exporter plugin allows attackers to control filenames used in PHP include/require statements, potentially reading sensitive local files via path traversal. The vulnerability stems from improper validation of user-supplied input before passing it to PHP's include/require functions.
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 WooCommerce Store Exporter plugin is installedCheck your WordPress site's wp-content/plugins/ directory for a folder named 'woocommerce-store-exporter' or use the WordPress admin Plugins page to list installed plugins.Affected if The plugin is installed and active in WordPress.
-
Identify the installed plugin versionLocate the main plugin file (typically plugin-root-file.php) and check the version header comment, or check the plugin's readme.txt file for the 'Stable tag' entry.Affected if The installed version matches or falls within an affected version range (compare your version to any officially listed vulnerable versions from the vendor).
-
Locate the file inclusion codeSearch the plugin source files for patterns like 'include(', 'require(', 'include_once(', or 'require_once(' where user-supplied parameters (e.g., $_GET, $_POST, $_REQUEST) are used as the included file path.Affected if Code exists that passes user-controlled input directly to PHP include/require functions without validation.
-
Identify the vulnerable parameter endpointExamine the HTTP request parameters (GET/POST) used in the identified inclusion code. Check which admin or frontend scripts handle these requests and note the parameter names.Affected if A parameter controllable via HTTP request is being used in the include/require statement without sanitization.
-
Test for path traversal capabilityIf you have access to test the affected endpoint, attempt a request with a path traversal payload (e.g., parameter=../../../../etc/passwd) to see if local files can be included.Affected if The application returns content from files outside the intended directory, confirming the LFI is exploitable.
You are affected if the WooCommerce Store Exporter plugin is installed, uses vulnerable include/require code, and allows user-controlled input to specify file paths without validation.
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 dataImplement strict input validation using allowlists for permitted file paths, or better yet, refactor to avoid dynamic file inclusion entirely. If a patched version is available from the vendor, upgrade immediately.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2025-60203 — 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-60203 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