InfiniteWP Client <= 1.3.7 - PHP Object Injection

2014-12-02 00:00
Marc-Alexandre Montpas

Strategic Overview

Status
Patched in 1.3.8
Affected Plugin
InfiniteWP Client
Affected Version
<= 1.3.7
CVSS
9.8Critical
Weakness type
CWE-502 · Deserialization of Untrusted Data
CVE
CVE pending
View all InfiniteWP Client vulnerabilities

At a glance

This record tracks a critical-severity Deserialization of Untrusted Data vulnerability in the InfiniteWP Client WordPress plugin, affecting versions <= 1.3.7. 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.3.8; sites on affected versions should update now. Disclosed December 2014, reported by Marc-Alexandre Montpas.

Vulnerability Overview

The InfiniteWP Client plugin for WordPress is vulnerable to PHP Object Injection in versions up to, and including, 1.3.7 via deserialization of untrusted input. This allows unauthenticated attackers to inject a PHP Object which can result in subsequent attacks Remote Code Injection, SQL Injection, Path Traversal, etc when a usable gadget is present.

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.3.7 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 InfiniteWP Client the fix is 1.3.8: builds <= 1.3.7 are affected, anything from 1.3.8 onward is not.

Remediation

Update to version 1.3.8, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Scanner
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/a71a1a7b-6299-44c5-b686-65f214986c27

Related records

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