dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-52445

HIGH · 8.8 CVSS v3.1 Published 2024-11-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 ModelTheme QRMenu Restaurant QR Menu Lite qrmenu-lite allows Object Injection.This issue affects QRMenu Restaurant QR Menu Lite: from n/a through <= 1.0.4.

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 (PHP Object Injection) vulnerability in the QRMenu Restaurant QR Menu Lite WordPress plugin versions up to 1.0.4 allows authenticated attackers to inject malicious PHP objects via unserialization of user-supplied data, potentially leading to remote code execution if magic methods exist in the plugin or connected libraries.

MitigationUpdate QRMenu Restaurant QR Menu Lite to the latest available version immediately. If no patched version exists, disable the plugin or implement Web Application Firewall (WAF) rules to block deserialization attacks 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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 QRMenu Restaurant QR Menu Lite plugin is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and search for 'QRMenu Restaurant QR Menu Lite' or inspect the wp-content/plugins directory for a folder containing 'qrmenu' or 'q-r-m-e-n-u' in the name
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed plugin version
    In WordPress admin, click on the plugin from the Installed Plugins list and view the version number displayed, or open the main plugin PHP file and look for the 'Version' header in the plugin comment block
    Affected if The version is 1.0.4 or lower (any version through 1.0.4)
  3. Confirm the plugin is active
    In WordPress admin > Plugins > Installed Plugins, check if 'QRMenu Restaurant QR Menu Lite' shows as 'Active' under the plugin status
    Affected if The plugin is enabled and running on the site
  4. Locate insecure deserialization in plugin code
    Use a file search or code analysis tool to scan plugin files for PHP unserialize() calls on user-supplied data (such as $_GET, $_POST, $_REQUEST, or database fields), then verify if those inputs are not validated with json_decode() or sanitized before deserialization
    Affected if Code contains unserialize() applied to untrusted input without prior validation

Your site is affected if the QRMenu Restaurant QR Menu Lite plugin is installed, active, and running version 1.0.4 or lower, with unsafe deserialization code present in the plugin files.

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

Update QRMenu Restaurant QR Menu Lite to the latest available version immediately. If no patched version exists, disable the plugin or implement Web Application Firewall (WAF) rules to block deserialization attacks until a fix is released.

Recommended fix Moderate confidence

Latest version of QRMenu Restaurant QR Menu Lite (newer than 1.0.4)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'QRMenu Restaurant QR Menu Lite' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. If no update is shown, manually download the latest version from the WordPress plugin repository and reinstall

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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