CVE-2016-15004

InfiniteWP Client <= 1.6.0 - Unauthenticated PHP Object Injection

2017-01-25 00:00
Yorick Koster,

Strategic Overview

Status
Patched in 1.6.1.1
Affected Plugin
InfiniteWP Client
Affected Version
< 1.6.1.1
CVSS
9.8Critical
Weakness type
CWE-502 · Deserialization of Untrusted Data
CVE
CVE-2016-15004
View all InfiniteWP Client vulnerabilities

At a glance

CVE-2016-15004 is a critical-severity Deserialization of Untrusted Data vulnerability in the InfiniteWP Client WordPress plugin, affecting versions < 1.6.1.1. 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 1.6.1.1; sites on affected versions should update now. Disclosed January 2017, reported by Yorick Koster,.

Vulnerability Overview

The InfiniteWP Client plugin for WordPress is vulnerable to PHP Object Injection in versions up to, and including, 1.6.0 via deserialization of untrusted input. This allows unauthenticated attackers to inject a PHP Object. The additional presence of a POP chain allows attackers to execute code on the site.

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 InfiniteWP Client < 1.6.1.1 takes no account at all. 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 InfiniteWP Client the fix is 1.6.1.1: builds < 1.6.1.1 are affected, anything from 1.6.1.1 onward is not.

Remediation

Update to version 1.6.1.1, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: 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: InfiniteWP Client 1.6.1.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

https://www.cve.org/CVERecord?id=CVE-2016-15004https://www.wordfence.com/threat-intel/vulnerabilities/id/8bd81f3c-f801-4fc6-b2db-754e5ebed688https://nvd.nist.gov/vuln/detail/CVE-2016-15004

Related records

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