timber/timber vulnerable to Deserialization of Untrusted Data

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.0 · CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H

EPSS

• CVE-2024-29800: 0.45% estimated exploitation activity in the next 30 days; percentile 39.43 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Timber is vulnerable to PHAR deserialization due to a lack of checking the input before passing it into the fileexists() function. If an attacker can upload files of any type to the server, he can pass in the phar:// protocol to unserialize the uploaded file and instantiate arbitrary PHP objects. This can lead to remote code execution especially when Timber is used with frameworks with documented POP chains like Wordpress/ vulnerable developer code. Details The vulnerability lies in the run function within the toJpg.php file. The two parameters passed into it are not checked or sanitized, hence an attacker could potentially inject malicious input leading to Deserialization of Untrusted Data, allowing for remote code execution: PoC Setup the following code in /var/www/html: vuln.php represents our use of Timber functions and phar-poc.php represents code with a vulnerable POP chain. As an attacker, we generate our PHAR payload using the following exploit script: Generate with:…

Published by the source

12 Apr 2024, 15:15 UTC

Last modified by the source

18 Apr 2024, 16:32 UTC

Source last checked

26 Oct 2026, 14:19 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6363-v5m4-fvq3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-29800

Advisory: timber/timber vulnerable to Deserialization of Untrusted Data
IDs: CVE-2024-29800, GHSA-6363-v5m4-fvq3
Record: https://patchnext.com/advisories/cve-2024-29800 (revision 1, source checked 26 Oct 2026, 14:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: timber/timber 2.1.0, 1.24.1, 1.23.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist timber/timber: affected >= 2.0.0, <= 2.0.0; >= 1.24.0, <= 1.24.0; >= 0.16.6, < 1.23.1; fixed in 1.24.1, 1.23.1, 2.1.0

## Suggested inspection (read-only)
- Packagist timber/timber: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on timber/timber.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6363-v5m4-fvq3 (GitHub-reviewed advisory GHSA-6363-v5m4-fvq3 lists affected ranges: Packagist timber/timber >=2.0.0 =1.24.0 =0.16.6 <1.23.1)

Commands are suggestions: review each one before running it.