dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-32835

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-24
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 WebToffee Import Export WordPress Users.This issue affects Import Export WordPress Users: from n/a through 2.5.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 the WebToffee Import Export WordPress Users plugin versions up to 2.5.3, where untrusted data is being deserialized without proper validation. This could allow an authenticated attacker to craft malicious serialized data that, when processed by the application, could lead to PHP object injection and potentially arbitrary code execution.

MitigationUpdate the WebToffee Import Export WordPress Users plugin to the latest version once available. If no patch exists, disable the plugin and use alternative solutions for user import/export functionality.

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. Confirm WebToffee Import Export plugin is installed
    Navigate to WordPress admin Dashboard > Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for a folder containing 'wt-import-export' or similar WebToffee plugin directories
    Affected if The plugin is not found in the WordPress installation
  2. Identify the exact installed version
    In WordPress admin, go to Plugins > Installed Plugins and look for the WebToffee Import Export WordPress Users plugin to view its version number displayed beneath the plugin name
    Affected if The version displayed is 2.5.3 or any version below 2.5.3 (meaning the version falls within the affected range 'up to 2.5.3')
  3. Verify deserialization is reachable
    Review the plugin settings and capabilities - the vulnerability requires the plugin's import functionality to be accessible, check if the import feature is enabled and accessible to authenticated users
    Affected if The plugin import functionality is active and authenticated users can access it, allowing them to supply potentially malicious serialized data

If the WebToffee Import Export WordPress Users plugin is installed at version 2.5.3 or below and its import feature is accessible to authenticated users, the environment is affected by this CVE.

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 the WebToffee Import Export WordPress Users plugin to the latest version once available. If no patch exists, disable the plugin and use alternative solutions for user import/export functionality.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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