dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-49684

HIGH · 7.2 CVSS v3.1 Published 2024-10-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 revmakx Backup and Staging by WP Time Capsule wp-time-capsule allows Object Injection.This issue affects Backup and Staging by WP Time Capsule: from n/a through <= 1.22.21.

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

This is a PHP Object Injection vulnerability in the WP Time Capsule plugin caused by unsafe deserialization of untrusted data. Attackers can potentially execute arbitrary code by injecting malicious PHP objects, especially if vulnerable classes exist in the application or connected libraries.

MitigationUpdate WP Time Capsule to the latest version. If a patch is unavailable, disable the plugin until a fix is released. Additionally, implement allowlist validation for any deserialized data and replace unsafe unserialize() calls with JSON-based serialization.

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
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 WP Time Capsule plugin is present
    Check for the wp-time-capsule directory in wp-content/plugins/ on the WordPress server
    Affected if The plugin directory exists on the filesystem
  2. Determine installed version
    Read the main plugin PHP file (typically wp-time-capsule.php) and extract the Version number from the plugin header comment
    Affected if The installed version matches the vulnerable version range (compare against the patched version)
  3. Confirm plugin is active
    Query the WordPress database: SELECT * FROM wp_options WHERE option_name = 'active_plugins'; or check via WordPress admin plugins list
    Affected if WP Time Capsule is enabled in the active_plugins option
  4. Check for unsafe deserialization calls
    Search plugin source files for unserialize() function usage: grep -r "unserialize" wp-content/plugins/wp-time-capsule/
    Affected if unserialize() calls exist in the plugin code without proper input validation

Environment is affected if WP Time Capsule plugin is installed, active, and contains the unsafe deserialization vulnerability in its code.

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 WP Time Capsule to the latest version. If a patch is unavailable, disable the plugin until a fix is released. Additionally, implement allowlist validation for any deserialized data and replace unsafe unserialize() calls with JSON-based serialization.

Have this fixed 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 help mitigating

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-49684 — 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-49684 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