dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-4606

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/100
Remediation priority · Elevated
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 BdThemes Ultimate Store Kit Elementor Addons.This issue affects Ultimate Store Kit Elementor Addons: from n/a through 2.0.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 deserialization vulnerability exists in BdThemes Ultimate Store Kit Elementor Addons plugin (versions up to 2.0.3). This vulnerability allows untrusted data to be deserialized, potentially enabling attackers to execute arbitrary code by crafting malicious serialized payloads.

MitigationUpdate Ultimate Store Kit Elementor Addons to the latest version beyond 2.0.3. If no patched version is available, consider disabling the plugin until a fix is released.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N

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 Ultimate Store Kit plugin installation
    Check the WordPress plugins directory (typically /wp-content/plugins/ultimate-store-kit/ or similar) via file manager, FTP, or WP-CLI: `wp plugin list --name='ultimate-store-kit'`
    Affected if The plugin directory exists on the server
  2. Identify the installed plugin version
    Open the main plugin file (usually ultimate-store-kit.php) and locate the 'Version' header in the plugin comment block, or run: `grep -i 'Version:' ultimate-store-kit.php`
    Affected if The reported version is 2.0.3 or any version prior to it (e.g., 2.0.2, 2.0.1, 1.x)
  3. Confirm the plugin author is BdThemes
    Verify the Plugin Author in the main plugin file matches 'BdThemes' or check via WordPress admin under Plugins > Installed Plugins > Ultimate Store Kit
    Affected if The author is BdThemes and version is 2.0.3 or earlier
  4. Check if the plugin is currently active
    In WordPress admin, go to Plugins > Installed Plugins and check the status, or query the database: `SELECT status FROM wp_options WHERE option_name LIKE '%ultimate_store_kit%'`
    Affected if The plugin is active; even if inactive, the vulnerable code may still be accessible via direct file inclusion

The environment is affected if the BdThemes Ultimate Store Kit plugin version is 2.0.3 or lower, regardless of whether it is active on the 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Ultimate Store Kit Elementor Addons to the latest version beyond 2.0.3. If no patched version is available, consider disabling the plugin until a fix is released.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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