CVE-2011-4106 json
TimThumb (timthumb.php) before 2.0 does not validate the entire source with the domain white list, which allows remote attackers to upload…
published 2013-10-26 13 y ago modified 2026-06-16 4 mo ago also EUVD-2011-4055
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 23.3%
- EPSS 23.3% chance of exploitation in 30 days, percentile 97%
- public exploits
- 2
- Exploit-DB
Summary
TimThumb (timthumb.php) before 2.0 does not validate the entire source with the domain white list, which allows remote attackers to upload and execute arbitrary code via a URL containing a white-listed domain in the src parameter, then accessing it via a direct request to the file in the cache directory, as exploited in the wild in August 2011.
Patch / fix
Timeline
- First public exploit (EDB-17602)
- Published
Exploit prediction
23.34% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-17872 Multiple WordPress Plugins - 'timthumb.php' File Upload webapps, 2011-09-19
- EDB-17602 WordPress Plugin TimThumb 1.32 - Remote Code Execution webapps, 2011-08-03
- code.google.com http://code.google.com/p/timthumb/issues/detail?id=212 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
markmaunder.com
/2011/08/02/technical-details-and-scripts-of-the-wordpress-timthumb-php-hack/
patch
-
code.google.com
/p/timthumb/issues/detail?id=212
exploit, patch
-
exploit-db.com
/exploits/17872
exploit
-
exploit-db.com
/exploits/17602
exploit
- binarymoon.co.uk /2011/08/timthumb-2/
-
openwall.com
/lists/oss-security/2011/11/03/4
mailing-list
- markmaunder.com /2011/08/01/zero-day-vulnerability-in-many-wordpress-themes/
Sources
- CVE List CVE-2011-4106
- NVD CVE-2011-4106
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.