CVE-2018-20987

Newsletters <= 4.6.8.5 - Object Injection

2018-03-12 00:00
Anonymous

Strategic Overview

Status
Patched in 4.6.8.6
Affected Plugin
Newsletters
Affected Version
< 4.6.8.6
CVSS
9.8Critical
Weakness type
CWE-502 · Deserialization of Untrusted Data
CVE
CVE-2018-20987
View all Newsletters vulnerabilities

At a glance

CVE-2018-20987 is a critical-severity Deserialization of Untrusted Data vulnerability in the Newsletters WordPress plugin, affecting versions < 4.6.8.6. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.6.8.6; sites on affected versions should update now. Disclosed March 2018.

Vulnerability Overview

The newsletters-lite plugin before 4.6.8.6 for WordPress has PHP object injection.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, 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 Newsletters < 4.6.8.6 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 Newsletters the fix is 4.6.8.6: builds < 4.6.8.6 are affected, anything from 4.6.8.6 onward is not.

Remediation

Update to version 4.6.8.6, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Newsletters: 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: Newsletters 4.6.8.6 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C