CVE-2018-20148

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

26.8% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2018-12-14 20:29 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 01:52 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 26.8% in the next 30 days (EPSS).
• Severity: 9.8 CRITICAL (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2018-12-14 20:29 UTC

Last modified

2026-06-17 01:52 UTC

Exploit probability

26.8% · EPSS, next 30 days

Weakness

CWE-502 · Unsafe deserialization

Record status

Modified

Affected

• WordPress < 4.9.9
• WordPress < 5.0.1
• Debian Linux 8.0
• Debian Linux 9.0

Attack profile CVSS 3.0 · 9.8

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2018-20148.md and follow it. Check whether this project is affected by CVE-2018-20148. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge