PropertyHive < 1.4.26 - Remote Code Execution

2018-11-20 00:00
Anonymous

Strategic Overview

Status
Patched in 1.4.26
Affected Plugin
Property Hive
Affected Version
< 1.4.26
CVSS
9.8Critical
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE pending
View all Property Hive vulnerabilities

At a glance

This record tracks a critical-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Property Hive WordPress plugin, affecting versions < 1.4.26. 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.4.26; sites on affected versions should update now. Disclosed November 2018.

Vulnerability Overview

The PropertyHive plugin for WordPress is vulnerable to Remote Code Execution in versions up to, and including, 1.4.25 via the custom_email_log_cron function. This allows unauthenticated attackers to execute code on the server.

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-94: Improper Control of Generation of Code ('Code Injection')

Reaching this weakness in Property Hive < 1.4.26 takes a caller who can reach the endpoint. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.

The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For Property Hive the fix is 1.4.26: builds < 1.4.26 are affected, anything from 1.4.26 onward is not.

Remediation

Update to version 1.4.26, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Property Hive: 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: Property Hive 1.4.26 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/02bb12db-0bc9-4c13-918f-1f90b500c165

Related records

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