dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-32587

HIGH · 8.1 CVSS v3.1 Published 2025-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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 pickupp WooCommerce Pickupp wc-pickupp allows PHP Local File Inclusion.This issue affects WooCommerce Pickupp: from n/a through <= 2.4.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 · moderate confidence

A path traversal vulnerability in the WooCommerce Pickupp plugin (wc-pickupp) allows authenticated or unauthenticated attackers to traverse directories and perform Local File Inclusion (LFI), potentially exposing sensitive server files or enabling code execution.

MitigationUpdate to the latest patched version of the WooCommerce Pickupp plugin. If no patch is available, disable the plugin immediately and implement WAF rules to block directory traversal patterns (../) in HTTP requests.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the WooCommerce Pickupp plugin version
    Check the plugin header in the main plugin file (wc-pickupp.php) located in wp-content/plugins/wc-pickupp/ directory. Look for the 'Version:' field in the plugin file header comments, or query the WordPress database in wp_options table for the plugin's version option if stored there.
    Affected if The installed version is older than the patched version released for CVE-2025-32587.
  2. Verify the plugin is active
    Query the WordPress database: SELECT * FROM wp_options WHERE option_name = 'active_plugins' and check if 'wc-pickupp/wc-pickupp.php' appears in the active plugins list, or use the WordPress admin interface to view installed plugins.
    Affected if The plugin is installed and active, making its vulnerable code accessible.
  3. Identify the vulnerable endpoint
    Review the plugin source code in wp-content/plugins/wc-pickupp/ directory, specifically looking for file inclusion functions (include, require, file_get_contents) that use user-supplied parameters without proper sanitization. Common vulnerable parameter names may include 'file', 'path', 'template', 'page', or 'load'.
    Affected if The plugin contains code that directly uses unsanitized input in file inclusion or file reading functions.
  4. Check for directory traversal patterns in HTTP requests
    Review web server access logs (Apache error.log, Nginx access.log) and WordPress debug logs for requests containing '../' sequences, particularly targeting the plugin endpoint (e.g., ?action=wc_pickupp&file=../../).
    Affected if Malicious requests with '../' patterns are present in logs targeting the plugin.
  5. Inspect for unauthorized file access
    Check if sensitive files outside the web root have been accessed by reviewing server access logs for unusual file paths, and verify the integrity of WordPress core and plugin files using tools like WordPress File Integrity Monitor or comparing file hashes.
    Affected if Files outside the expected plugin directory have been accessed or modified.

You are affected if the WooCommerce Pickupp plugin is active and its version predates the patched release for CVE-2025-32587, or if directory traversal attempts appear in your server logs targeting the plugin.

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 to the latest patched version of the WooCommerce Pickupp plugin. If no patch is available, disable the plugin immediately and implement WAF rules to block directory traversal patterns (../) in HTTP requests.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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