| Name | CVE-2017-1000600 |
| Description | WordPress version <4.9 contains a CWE-20 Input Validation vulnerability in thumbnail processing that can result in remote code execution. This attack appears to be exploitable via thumbnail upload by an authenticated user and may require additional plugins in order to be exploited however this has not been confirmed at this time. This issue appears to have been partially, but not completely fixed in WordPress 4.9 |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| wordpress (PTS) | bullseye (security), bullseye | 5.7.11+dfsg1-0+deb11u1 | fixed |
| bookworm, bookworm (security) | 6.1.6+dfsg1-0+deb12u1 | fixed |
| sid, trixie | 6.6.1+dfsg1-1 | fixed |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|
| wordpress | source | (unstable) | 4.9.1+dfsg-1 | | | |
Notes
[stretch] - wordpress <postponed> (requires authenticated user, root cause in PHP phar:// unserialization and requires thorough application-level checks, no upstream patch)
[jessie] - wordpress <postponed> (requires authenticated user, root cause in PHP phar:// unserialization and requires thorough application-level checks, no upstream patch)
https://www.theregister.co.uk/2018/08/20/php_unserialisation_wordpress_vuln/
https://cdn2.hubspot.net/hubfs/3853213/us-18-Thomas-It's-A-PHP-Unserialization-Vulnerability-Jim-But-Not-As-We-....pdf
https://twitter.com/_s_n_t/status/1030573635617124353 (possible mitigation)
https://www.slideshare.net/_s_n_t/php-unserialization-vulnerabilities-what-are-we-missing (75-76, pre-4.9 POP chain)
https://github.com/WordPress/WordPress/commit/0a3b7d8e31def538cf531791efe8bf33e6e243cc (4.9 POP chain break)
Wordpress before 4.9 is vulnerable on its own. After 4.9 you need to have
vulnerable module installed on the site as well. Due to an incomplete fix
in 4.9 there exists CVE-2018-1000773.