dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-29800

HIGH · 8.0 CVSS v3.1 Published 2024-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
86/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 Timber Team & Contributors Timber.This issue affects Timber: from n/a through 1.23.0.

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 of untrusted data vulnerability in the Timber WordPress plugin (versions through 1.23.0) allows attackers to potentially execute arbitrary code by supplying malicious serialized data that gets processed without proper validation.

MitigationUpgrade Timber to version 1.23.1 or later which contains the security fix; also review WordPress installations for any signs of compromise.

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/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 Timber plugin installation
    Check if the Timber plugin directory exists in your WordPress installation, typically at wp-content/plugins/timber-library/ or wp-content/plugins/timber/. Use a file manager or command line: ls wp-content/plugins/ | grep timber
    Affected if The Timber plugin directory does not exist (not installed)
  2. Determine the installed Timber version
    Open the main Timber plugin PHP file (usually timber-library.php or Timber.php in the plugin directory) and locate the 'Version' header in the plugin comment block at the top. Alternatively, check wp-content/plugins/timber-library/readme.txt for the 'Stable tag' entry
    Affected if Unable to locate version information (plugin may not be properly installed)
  3. Compare your version against the affected range
    Compare the version number you found against the affected range: versions 1.23.0 and earlier are vulnerable. Versions 1.23.1 and later contain the fix. For example, if your version is 1.22.0, 1.23.0, or 1.23.0.1, you are in the affected range
    Affected if Your Timber version is 1.23.0 or earlier (e.g., 1.22.0, 1.21.0, etc.)
  4. Verify the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm whether Timber is currently activated. Or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' LIKE '%timber%'
    Affected if Timber is installed but not currently active (vulnerability not currently exploitable in your running environment)

You are affected if the Timber plugin is installed, active, and your installed version is 1.23.0 or earlier.

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

Upgrade Timber to version 1.23.1 or later which contains the security fix; also review WordPress installations for any signs of compromise.

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