dbcve.org
Product Import Export For WoocommerceWordPress extension · Webtoffee

CVE-2024-22152

HIGH · 7.2 CVSS v3.1 Published 2024-01-24
Fix available
A fix is available. Upgrade to 2.3.8 or later.
See remediation →
78/100
Remediation priority · High
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
Unrestricted Upload of File with Dangerous Type vulnerability in WebToffee Product Import Export for WooCommerce.This issue affects Product Import Export for WooCommerce: from n/a through 2.3.7.

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

An unrestricted file upload vulnerability exists in WebToffee Product Import Export for WooCommerce plugin versions through 2.3.7. The plugin fails to properly validate uploaded file types, allowing attackers to upload dangerous executable files (such as PHP scripts) that could lead to remote code execution on the server.

MitigationUpdate to the latest patched version of the plugin. If no patch is available, implement server-side file type validation using magic bytes/file content inspection, restrict upload directory execution permissions, and consider disabling the import functionality until a fix is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Product Import Export For WoocommerceWordPress extension
Affected:< 2.3.8

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

CVSS:3.1/AV:N/AC:L/PR:H/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 the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, locate 'WebToffee Product Import Export for WooCommerce', and note the version number displayed. Alternatively, check the plugin's main PHP file for the 'Version' header in the plugin comment block.
    Affected if The installed version is any version lower than 2.3.8 (for example, 2.3.7, 2.3.6, or earlier).
  2. Confirm the plugin import functionality is active
    Navigate to WooCommerce > Product Import Export (or similar menu item provided by the plugin) in the WordPress admin dashboard. Verify the import tab or feature is present and accessible.
    Affected if The import functionality is enabled and accessible to users with appropriate permissions.
  3. Identify the upload endpoint accessibility
    Check if the WordPress site's XML-RPC or REST API endpoints related to the plugin are publicly accessible. This can be done by attempting to access common plugin import routes or reviewing the site's access control settings.
    Affected if The import endpoint is accessible without additional authentication beyond standard WordPress user privileges.

You are affected if the plugin version is below 2.3.8 AND the product import/export functionality is active and accessible on your WordPress site.

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
Upgrade available Upgrade to 2.3.8 or later
Fixed in 2.3.8
Interim mitigation

Update to the latest patched version of the plugin. If no patch is available, implement server-side file type validation using magic bytes/file content inspection, restrict upload directory execution permissions, and consider disabling the import functionality until a fix is available.

Recommended fix High confidence

2.3.8

  1. Backup your WordPress site and database before making any changes
  2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. Locate 'Product Import Export For WooCommerce' by WebToffee
  4. Click 'Update now' or manually update to version 2.3.8
  5. Verify the plugin version shows 2.3.8 after update
  6. Test that product import/export functionality works correctly

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

Fix this in Product Import Export For Woocommerce Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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