dbcve.org
Product Import Export For WoocommerceWordPress extension · Webtoffee

CVE-2024-30231

HIGH · 7.2 CVSS v3.1 Published 2024-03-26
Fix available
A fix is available. Upgrade to after 2.4.1 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.4.1.

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 the WebToffee Product Import Export for WooCommerce plugin (versions through 2.4.1). The plugin fails to properly validate uploaded file types before storage, allowing attackers to potentially upload malicious executable files (such as PHP scripts) to the server. This could lead to remote code execution and complete compromise of the WordPress site.

MitigationUpgrade to the latest version of Product Import Export for WooCommerce immediately. If no patched version is available, disable the plugin or implement web server-level file type restrictions (e.g., via .htaccess or nginx configuration) to prevent executable file uploads.

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.4.1

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. Verify plugin is installed
    Navigate to WordPress admin > Plugins and locate 'WebToffee Product Import Export For WooCommerce' in the list of installed plugins
    Affected if The plugin appears in the installed plugins list
  2. Check installed plugin version
    In the Plugins list, look at the version number displayed under the plugin name, or click into the plugin page to view the Details section showing version
    Affected if The version listed is 2.4.1 or lower (any version through 2.4.1)
  3. Confirm import functionality is active
    Check if the plugin menu appears in the WordPress sidebar (typically under WooCommerce or a dedicated WebToffee section) and the Import feature is accessible without being disabled
    Affected if The Import/Export menu is visible and the import feature can be accessed
  4. Inspect uploads directory for suspicious files
    Via FTP or file manager, examine the /wp-content/uploads/ directory (and subdirectories) for recently added .php, .phtml, .php5, .phar or other executable file types that were not intentionally uploaded through legitimate means
    Affected if Unexpected PHP files or other executable scripts are found in upload directories

A user is affected if the WebToffee Product Import Export For WooCommerce plugin is installed with version 2.4.1 or lower and the import functionality is accessible.

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 a release after 2.4.1
Interim mitigation

Upgrade to the latest version of Product Import Export for WooCommerce immediately. If no patched version is available, disable the plugin or implement web server-level file type restrictions (e.g., via .htaccess or nginx configuration) to prevent executable file uploads.

Recommended fix Moderate confidence

Latest version of Product Import Export For WooCommerce (check WebToffee website or WordPress plugin repository for version higher than 2.4.1)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find 'Product Import Export For WooCommerce' (by WebToffee)
  4. 4. If an update is available, click 'Update Now'
  5. 5. Verify the update completes successfully
  6. 6. Test the import/export functionality to ensure the plugin still works correctly
  7. 7. Check the plugin changelog or WebToffee's official site to confirm the version includes the security fix for CVE-2024-30231

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
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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-2024-30231 — 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-30231 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