Deserialization in WordPress

CVE-2018-20148

In WordPress before 4.9.9 and 5.x before 5.0.1, contributors could conduct PHP object injection attacks via crafted metadata in a wp.getMediaItem XMLRPC call. This is caused by mishandling of serialized data at phar:// URLs in the wp_get_attachment_thumb_file function in wp-includes/post.php.

Vulnerability class: Insecure Deserialization

Published · last modified .

CVSS v3 metric

CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

EPSS exploit prediction

EPSS: 0.268 (98.0th percentile), scored .

Moderate probability of exploitation in the next 30 days — watch for active exploitation reports. 98th percentile — 98.0% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2018-20148: held from 0.268 to 0.268.

EPSS over last 30 days · oldest: 0.268 · newest: 0.268 · change: 0.000

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2018-20148?
CVE-2018-20148 is a critical-severity vulnerability in WordPress, classified under Deserialization of Untrusted Data. CVSS score: 9.8/10. Published 2018-12-14.
How severe is CVE-2018-20148?
Critical severity. CVSS v3 base score is 9.8 out of 10.
Is CVE-2018-20148 known to be exploited?
11 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.