dbcve.org
WholesalexWordPress extension · Wpxpo

CVE-2024-30224

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-28
Fix available
A fix is available. Upgrade to 1.3.3 or later.
See remediation →
100/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
Deserialization of Untrusted Data vulnerability in Wholesale Team WholesaleX.This issue affects WholesaleX: from n/a through 1.3.2.

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

Deserialization of Untrusted Data vulnerability in WholesaleX plugin for WooCommerce allows unauthenticated attackers to potentially execute arbitrary code via malicious serialized data, given the critical CVSS 9.8 rating indicating ease of exploitation and severe impact.

MitigationUpdate WholesaleX to the latest version beyond 1.3.2 immediately; audit logs and systems for indicators of compromise since deserialization flaws can allow remote code execution.

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
WholesalexWordPress extension
Affected:< 1.3.3

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/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. Check WholesaleX plugin version
    Navigate to WordPress Admin > Plugins > Installed Plugins and locate WholesaleX. The version number is displayed below the plugin name. Alternatively, inspect the main plugin file (wholesalex.php) in /wp-content/plugins/wholesalex/ and look for the Version header in the plugin comment block.
    Affected if The installed version is lower than 1.3.3 (versions 1.3.2 and below are affected)
  2. Confirm plugin is active
    Verify in WordPress Admin > Plugins that WholesaleX shows as 'Active'. The deserialization vulnerability is only exploitable when the plugin is loaded and its AJAX handlers or public endpoints are accessible.
    Affected if The plugin is active and running on the site
  3. Identify public-facing endpoints
    Check the plugin directory /wp-content/plugins/wholesalex/ for AJAX handlers (wp-admin/admin-ajax.php) or REST API endpoints that process serialized data. Inspect PHP files containing unserialize() calls on input from $_POST, $_GET, or $_REQUEST.
    Affected if The plugin exposes endpoints that accept and process serialized data without validation
  4. Review server access logs
    Examine HTTP access logs for POST requests to /wp-admin/admin-ajax.php or REST API endpoints with action parameters related to WholesaleX. Look for unusual serialized payloads in request bodies.
    Affected if There are suspicious requests containing serialized PHP data targeting WholesaleX endpoints

A site is affected if WholesaleX is installed with version below 1.3.3 and the plugin is active, allowing unauthenticated attackers to inject malicious serialized data via public endpoints.

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 1.3.3 or later
Fixed in 1.3.3
Interim mitigation

Update WholesaleX to the latest version beyond 1.3.2 immediately; audit logs and systems for indicators of compromise since deserialization flaws can allow remote code execution.

Recommended fix High confidence

WholesaleX 1.3.3

  1. Update WholesaleX plugin to version 1.3.3 or later via WordPress admin (Dashboard > Plugins > Updates)
  2. If automatic update is not available, manually download WholesaleX 1.3.3 from the official WordPress plugin repository
  3. Navigate to Plugins > Add New > Upload Plugin to upload and install the new version
  4. After upgrading, verify the plugin is active and test wholesale pricing functionality to confirm proper operation

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

Fix this in Wholesalex Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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