Strategic Overview
- Status
- Patched in 3.7.28
- Affected Core
- WordPress 5.0
- Affected Version
3.7 – 5.0 · 15 branches- CVSS
- 7.5High
- Weakness type
- CWE-502 · Deserialization of Untrusted Data
- CVE
CVE-2018-1000773
At a glance
CVE-2018-1000773 is a high-severity Deserialization of Untrusted Data vulnerability in the WordPress 5.0 WordPress release line, affecting 3.7 – 5.0 · 15 branches. It carries a CVSS score of 7.5 (reachable over the network; high confidentiality, integrity, availability impact). The issue is fixed in version 3.7.28; sites on affected versions should update now. Disclosed September 2018, reported by Sam Thomas.
Vulnerability Overview
WordPress Core versions before 5.0.1 contain a CWE-20 Input Validation vulnerability in thumbnail processing that can result in remote code execution due to an incomplete fix for CVE-2017-1000600. 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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-502: Deserialization of Untrusted Data
Reaching this weakness in WordPress 5.0 3.7 – 5.0 · 15 branches takes a caller who can reach the endpoint. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.
A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For WordPress 5.0 the fix is 3.7.28: builds 3.7 – 5.0 · 15 branches are affected, anything from 3.7.28 onward is not.
Remediation
Update to one of the following versions, or a newer patched version: 3.7.28, 3.8.28, 3.9.26, 4.0.25, 4.1.25, 4.2.22, 4.3.18, 4.4.17, 4.5.16, 4.6.13, 4.7.12, 4.8.8, 4.9.9, 5.0.1
How does WordSec protect against this?
The attempt arrives as an ordinary request to WordPress 5.0: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: updating to 3.7.28 is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Same weakness class
- 9.8CVE-2024-31211: WordPress Core 6.4.0 - 6.4.1 RCE POP Chain
CVE-2024-31211 - 9.8CVE-2021-29476: WordPress Core < 5.5.3 PHP Object Injection Gadget
CVE-2021-29476 - 8.8CVE-2020-28032: WordPress Core < 5.5.2 Deserialization Gadget
CVE-2020-28032 - 8.8CVE-2018-20148: WordPress Core < 5.0.1 PHP Object Injection
CVE-2018-20148
Other vulnerabilities in WordPress 5.0
- 9.8CVE-2026-63030: WordPress Core 6.9 - 7.0.1 Remote Code Execution
CVE-2026-63030 - 9.8WordPress Core < 6.0.3 SQL Injection via WP_Date_Query
- 9.8CVE-2017-16510: WordPress Core SQL Injection
CVE-2017-16510 - 9.8CVE-2017-14723: WordPress Core < 4.8.2 SQL Injection
CVE-2017-14723 - 9.8CVE-2007-6013: WordPress Core 1.5 - 2.3.1 Authorization Bypass
CVE-2007-6013 - 9.8CVE-2007-6318: WordPress Core < 2.3.2 SQL Injection
CVE-2007-6318 - 9.8CVE-2007-4894: WordPress Core & WordPress MU < 1.2.5a - SQL Injection
CVE-2007-4894 - 9.8CVE-2007-1277: WordPress Core 2.2.1 Backdoor
CVE-2007-1277
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C