dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-4387

HIGH · 8.8 CVSS v3.1 Published 2025-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
The Abandoned Cart Pro for WooCommerce plugin contains an authenticated arbitrary file upload vulnerability due to missing file type validation in the wcap_add_to_cart_popup_upload_files function in all versions up to, and including, 9.16.0. This makes it possible for an authenticated attacker, with subscriber-level access and above, to upload arbitrary files on the affected site's server which may allow for either remote or local code execution depending on the server configuration.

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 confidence

The Abandoned Cart Pro for WooCommerce plugin versions up to 9.16.0 contains an authenticated arbitrary file upload vulnerability in the wcap_add_to_cart_popup_upload_files function. Due to missing file type validation, any authenticated user with subscriber-level access or higher can upload arbitrary files to the server, potentially achieving remote code execution.

MitigationImplement proper file type validation using allowlist-based checks, add nonce verification, enforce capability checks (require administrator-level access), and store uploads outside the web root or disable script execution in upload directories.

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

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

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

  1. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Abandoned Cart Pro for WooCommerce' to see the version number. Alternatively, inspect the main plugin file (usually abandoned-cart-pro-for-woocommerce.php) and look for the 'Version' header comment.
    Affected if The installed version is 9.16.0 or lower.
  2. Verify vulnerable function exists
    Search the plugin directory for the function wcap_add_to_cart_popup_upload_files. This is typically found in includes or admin folders. Use grep: grep -r 'wcap_add_to_cart_popup_upload_files' /path/to/wp-content/plugins/abandoned-cart-pro-for-woocommerce/
    Affected if The function wcap_add_to_cart_popup_upload_files exists in the plugin code.
  3. Confirm function is hooked to accessible action
    Search for add_action or add_filter calls that register wcap_add_to_cart_popup_upload_files to a publicly accessible hook (such as wp_ajax_wcap_add_to_cart_popup_upload_files or wp_ajax_nopriv_). Check if the action is registered with wp_ajax_ (requiring auth) or wp_ajax_nopriv_ (allowing unauthenticated access).
    Affected if The function is hooked to an AJAX action accessible to authenticated users with subscriber-level access or higher.
  4. Inspect file upload handling for validation gaps
    Examine the wcap_add_to_cart_popup_upload_files function code. Look for $_FILES processing, specifically check if there is any file type validation using wp_check_filetype, mime type checking, or an allowlist of permitted extensions.
    Affected if The function contains no file type validation, no nonce verification, and no capability check requiring administrator-level access.

You are affected if the plugin version is 9.16.0 or lower AND the wcap_add_to_cart_popup_upload_files function exists with missing file type validation and weak access controls.

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 proper file type validation using allowlist-based checks, add nonce verification, enforce capability checks (require administrator-level access), and store uploads outside the web root or disable script execution in upload directories.

Recommended fix High confidence

Upgrade to Abandoned Cart Pro for WooCommerce version 9.17.0 or later

  1. 1. Back up the entire WordPress site, including the database and all files.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate the 'Abandoned Cart Pro for WooCommerce' plugin.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Alternatively, download the latest version from the WordPress plugin repository or from Tychesoftwares (the developer) and manually upload it via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the new version number reflects 9.17.0 or later in the plugins list.
  7. 7. Test the abandoned cart functionality to ensure the plugin continues to work correctly after the update.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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 locally
dbcve dependency scanner

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