dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-48124

HIGH · 7.5 CVSS v3.1 Published 2025-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Holest Engineering Spreadsheet Price Changer for WooCommerce and WP E-commerce – Light excel-like-price-change-for-woocommerce-and-wp-e-commerce-light allows Path Traversal.This issue affects Spreadsheet Price Changer for WooCommerce and WP E-commerce – Light: from n/a through <= 2.4.37.

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 confidence

The Spreadsheet Price Changer plugin for WooCommerce contains a path traversal vulnerability (CWE-22) that allows attackers to use '../' sequences in file path parameters to access files outside the intended web root directory. This improper limitation of pathname to restricted directory can be exploited without authentication, potentially exposing sensitive system files or configuration data.

MitigationImplement strict input validation with path canonicalization - validate that resolved file paths remain within allowed directories, use basename() to strip directory traversal sequences, and whitelist permitted file access paths. Alternatively, disable the affected file operation until a vendor patch is available.

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 plugin installation
    Check your WordPress plugins directory for the Spreadsheet Price Changer plugin folder, typically found in wp-content/plugins/ directory, or view installed plugins via WordPress admin under Plugins > Installed Plugins
    Affected if The Spreadsheet Price Changer plugin is present in your WordPress installation
  2. Identify installed plugin version
    Read the plugin header comment from the main plugin PHP file (usually named spreadsheet-price-changer.php or similar in wp-content/plugins/spreadsheet-price-changer/) which contains the Version field, or check the plugin row in WordPress admin plugins list
    Affected if The installed version matches or falls within an affected version range that has not been patched
  3. Verify file operation functionality is active
    Check the plugin settings page in WordPress admin under WooCommerce menu for any spreadsheet import/export or file handling features that may be exposed; also verify the plugin PHP files contain file read/write operations using parameters that could accept user input
    Affected if The plugin file operation feature is enabled and accessible
  4. Check plugin endpoint accessibility
    Examine your web server access logs for requests to plugin endpoints (commonly in /wp-content/plugins/spreadsheet-price-changer/ or /?wc-api=spreadsheet-price-changer) and verify whether these endpoints are accessible without authentication
    Affected if The plugin endpoints are publicly accessible without requiring authentication
  5. Review logs for exploitation indicators
    Search web server access and error logs for patterns containing '../' or '..\' sequences in requests to plugin-related URLs, particularly any unusual file path requests that may indicate path traversal attempts
    Affected if Logs contain requests with directory traversal sequences targeting the plugin

You are affected if the Spreadsheet Price Changer plugin is installed and its file operation feature is accessible without authentication, regardless of whether exploitation attempts are observed in logs.

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

Implement strict input validation with path canonicalization - validate that resolved file paths remain within allowed directories, use basename() to strip directory traversal sequences, and whitelist permitted file access paths. Alternatively, disable the affected file operation until a vendor patch is available.

Recommended fix Moderate confidence

Update to the latest version available (newer than 2.4.37, which should contain the path traversal fix)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Spreadsheet Price Changer for WooCommerce and WP E-commerce – Light' (excel-like-price-change-for-woocommerce-and-wp-e-commerce-light)
  4. 4. If an update is available, click 'Update Now' to update the plugin to the latest version
  5. 5. Alternatively, download the latest version from the WordPress Plugin Repository or the vendor's official source
  6. 6. After updating, verify the plugin is functioning correctly on the site

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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