dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-52414

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Anthony Carbon WDES Responsive Mobile Menu wdes-responsive-mobile-menu allows Object Injection.This issue affects WDES Responsive Mobile Menu: from n/a through <= 5.3.18.

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 · high confidence

A deserialization of untrusted data vulnerability in the WDES Responsive Mobile Menu WordPress plugin (versions <= 5.3.18) allows attackers to inject malicious PHP objects via unsafe deserialization, potentially leading to remote code execution depending on available gadget chains.

MitigationUpgrade to a patched version of WDES Responsive Mobile Menu; if no patched version is available, disable the plugin until remediation is possible.

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
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. Locate the WDES Responsive Mobile Menu plugin
    Check the /wp-content/plugins/ directory for a folder named 'wd-responsive-mobile-menu' or similar variant. In WordPress admin, go to Plugins > Installed Plugins and look for 'WDES Responsive Mobile Menu'.
    Affected if The plugin folder exists in the WordPress installation's plugins directory.
  2. Determine the installed plugin version
    Open the main plugin PHP file (typically in the plugin folder root) and look for the version comment in the plugin header, or check the plugin's readme.txt file for the 'Stable tag' version number.
    Affected if The version shown is 5.3.18 or any lower version number.
  3. Verify the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and check if 'WDES Responsive Mobile Menu' shows as 'Active', or run 'wp plugin list --status=active' via WP-CLI to confirm active status.
    Affected if The plugin is currently activated on the WordPress site.
  4. Identify unsafe deserialization entry points
    Examine the plugin's PHP files for usage of unserialize() function on user-controlled input (such as $_GET, $_POST, $_REQUEST, or cookie values). Common patterns include: unserialize($_GET['param']), unserialize($_POST['data']), or similar. Search the plugin directory for 'unserialize' function calls.
    Affected if The plugin code contains unserialize() calls processing input from external sources without prior validation.

If the plugin is installed, active, and its version is 5.3.18 or lower, the environment is vulnerable to CVE-2024-52414.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of WDES Responsive Mobile Menu; if no patched version is available, disable the plugin until remediation is possible.

Recommended fix Moderate confidence

Latest version available on wordpress.org (greater than 5.3.18)

  1. Check current plugin version in WordPress admin under Plugins > Installed Plugins
  2. Update WDES Responsive Mobile Menu plugin to the latest available version through WordPress plugin updates, or manually download the latest version from wordpress.org/plugins/wdes-responsive-mobile-menu/
  3. After updating, verify the site functionality remains intact

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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