CVE-2024-27985

PropertyHive <= 2.0.9 - Authenticated (Subscriber+) PHP Object Injection

2024-03-13 00:00
Anonymous

Strategic Overview

Status
Patched in 2.0.10
Affected Plugin
Property Hive
Affected Version
<= 2.0.9
CVSS
8.8High
Weakness type
CWE-502 · Deserialization of Untrusted Data
CVE
CVE-2024-27985
View all Property Hive vulnerabilities

At a glance

CVE-2024-27985 is a high-severity Deserialization of Untrusted Data vulnerability in the Property Hive WordPress plugin, affecting versions <= 2.0.9. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.0.10; sites on affected versions should update now. Disclosed March 2024.

Vulnerability Overview

The PropertyHive plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.0.9 via deserialization of untrusted input through the 'body' parameter. This makes it possible for attackers, with subscriber-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable plugin. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.

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 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

Property Hive <= 2.0.9 carries this weakness at body, and reaching it takes an account at Subscriber level or above. 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 Property Hive the fix is 2.0.10: builds <= 2.0.9 are affected, anything from 2.0.10 onward is not.

Remediation

Update to version 2.0.10, or a newer patched version

How does WordSec protect against this?

An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: 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 2.0.10 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-27985https://www.wordfence.com/threat-intel/vulnerabilities/id/f7b24b7c-1a15-4b38-b59e-bcad39cc4340https://nvd.nist.gov/vuln/detail/CVE-2024-27985

Related records

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