CVE-2024-23513

PropertyHive <= 2.0.5 - Unauthenticated PHP Object Injection via propertyhive_currency

2024-01-30 00:00
beluga

Strategic Overview

Status
Patched in 2.0.6
Affected Plugin
Property Hive
Affected Version
<= 2.0.5
CVSS
8.1High
Weakness type
CWE-502 · Deserialization of Untrusted Data
CVE
CVE-2024-23513
View all Property Hive vulnerabilities

At a glance

CVE-2024-23513 is a high-severity Deserialization of Untrusted Data vulnerability in the Property Hive WordPress plugin, affecting versions <= 2.0.5. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.0.6; sites on affected versions should update now. Disclosed January 2024, reported by beluga.

Vulnerability Overview

The PropertyHive plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.0.5 via deserialization of untrusted input from the 'propertyhive_currency' cookie value. This makes it possible for unauthenticated attackers to inject a PHP Object. No 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, 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

Property Hive <= 2.0.5 carries this weakness at propertyhive_currency, and reaching it 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 Property Hive the fix is 2.0.6: builds <= 2.0.5 are affected, anything from 2.0.6 onward is not.

Remediation

Update to version 2.0.6, 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: Property Hive 2.0.6 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-2024-23513https://www.wordfence.com/threat-intel/vulnerabilities/id/d8ee82cf-916c-41e9-82d2-f25cc7a632aehttps://nvd.nist.gov/vuln/detail/CVE-2024-23513

Related records

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