dbcve.org
One Click Demo ImportWordPress extension · Ocdi

CVE-2024-34433

HIGH · 7.2 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 3.2.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
Deserialization of Untrusted Data vulnerability in OCDI One Click Demo Import.This issue affects One Click Demo Import: from n/a through 3.2.0.

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 in the One Click Demo Import WordPress plugin allows untrusted data to be deserialized, which in PHP contexts can lead to remote code execution depending on available gadget chains in the application environment.

MitigationUpdate to the latest version of One Click Demo Import when available, and audit the plugin's data handling to ensure any unserialize() calls are removed or properly validated with allowlist-based checks.

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
One Click Demo ImportWordPress extension
Affected:< 3.2.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 One Click Demo Import plugin is installed
    Check for the plugin directory at wp-content/plugins/one-click-demo-import/ or look for 'One Click Demo Import' in WordPress plugin list at /wp-admin/plugins.php
    Affected if Plugin directory or listing exists in the WordPress installation
  2. Check installed plugin version
    Open wp-content/plugins/one-click-demo-import/one-click-demo-import.php and look for 'Version:' in the plugin header comment, or check the Version field in wp-admin/plugins.php
    Affected if Version number is present and less than 3.2.1
  3. Confirm plugin is active
    Check WordPress admin plugins page or query wp_options table for option_name='active_plugins' containing 'one-click-demo-import'
    Affected if Plugin appears in active_plugins array or shows as 'Active' in admin
  4. Locate unserialize calls in plugin code
    Search plugin files for unserialize() calls: grep -r "unserialize" wp-content/plugins/one-click-demo-import/
    Affected if Any unserialize() call is found that processes data from $_POST, $_GET, $_REQUEST, or imported XML/JSON files
  5. Check if demo import functionality is accessible
    Review if the plugin's import endpoints (usually in admin-ajax.php or custom REST routes) accept and process unserialize-able data from import files or form submissions
    Affected if Import functionality processes serialized data without allowlist validation

User is affected if One Click Demo Import plugin version is below 3.2.1, the plugin is active, and unserialize() calls handle untrusted import data.

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

Update to the latest version of One Click Demo Import when available, and audit the plugin's data handling to ensure any unserialize() calls are removed or properly validated with allowlist-based checks.

Recommended fix High confidence

One Click Demo Import version 3.2.1

  1. Update the One Click Demo Import plugin to version 3.2.1 or later through the WordPress plugin repository, or reinstall the plugin from the official WordPress plugin directory to obtain the patched version.

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

Fix this in One Click Demo Import 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 the upgrade done

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