dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-49218

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-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 Al Imran Akash Recently recently-viewed-most-viewed-and-sold-products-for-woocommerce allows Object Injection.This issue affects Recently: from n/a through <= 1.1.

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 PHP Object Injection vulnerability exists in the 'Recently' plugin for WooCommerce (recently-viewed-most-viewed-and-sold-products-for-woocommerce). The plugin deserializes untrusted data without proper validation, allowing attackers to inject malicious PHP objects. This can lead to remote code execution, file inclusion, or database compromise depending on available PHP magic methods and the application's object landscape.

MitigationUpdate the 'Recently' plugin to the latest patched version immediately. If no update is available, disable the plugin until a fix is released, and review access logs for indicators of exploitation.

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. Confirm the Recently plugin is installed
    Log into WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'Recently Viewed Most Viewed And Sold Products For WooCommerce' in the list. Alternatively, check the wp-content/plugins directory for a folder named ' Recently' or check the database wp_options table for the active_plugins entry.
    Affected if The plugin appears in the list of installed plugins and is activated
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and click 'View Details' on the Recently plugin, or inspect the main plugin PHP file header for the Version field. If using CLI, check the plugin main file: wp-content/plugins/ recently-viewed-most-viewed-and-sold-products-for-woocommerce/[main-file-name].php
    Affected if The version number is lower than the patched version released for this CVE (compare your version to the vendor's security advisory)
  3. Check for user input handling that accepts serialized data
    Review the plugin code for usage of PHP unserialize() function, particularly on data derived from user input such as $_GET, $_POST, $_COOKIE, or database fields that may contain attacker-controlled serialized content. Search plugin PHP files for patterns like 'unserialize($_' or 'unserialize($' with external sources.
    Affected if The plugin code contains unserialize() calls processing untrusted input without prior sanitization or validation
  4. Audit access logs for exploitation indicators
    Examine web server access logs (Apache/Nginx) and WordPress activity logs for unusual requests to plugin endpoints containing serialized PHP objects, PHP payload patterns, or O: (object serialization) signatures in query parameters, POST data, or cookies.
    Affected if Logs contain requests with serialized PHP objects being passed to plugin parameters, especially with known PHP magic method triggers like '__destruct' or '__wakeup'
  5. Inspect database for malicious serialized entries
    Query the WordPress database (wp_options table and any custom plugin tables) for stored values containing serialized PHP objects that were not created by legitimate plugin functionality. Look for unusually long serialized strings or patterns starting with 'O:' followed by numbers.
    Affected if Database contains serialized data that was not legitimately created by the plugin's normal operation

You are affected if the Recently plugin is installed and active, your installed version has not been patched for this CVE, and your environment processes untrusted serialized data through the plugin.

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 'Recently' plugin to the latest patched version immediately. If no update is available, disable the plugin until a fix is released, and review access logs for indicators of exploitation.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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