CVE-2024-8490

PropertyHive <= 2.0.19 - Cross-Site Request Forgery via save_account_details

2024-09-16 00:00
wesley (wcraft)

Strategic Overview

Status
Patched in 2.0.20
Affected Plugin
Property Hive
Affected Version
<= 2.0.19
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-8490
View all Property Hive vulnerabilities

At a glance

CVE-2024-8490 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Property Hive WordPress plugin, affecting versions <= 2.0.19. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.0.20; sites on affected versions should update now. Disclosed September 2024, reported by wesley (wcraft).

Vulnerability Overview

The PropertyHive plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0.19. This is due to missing or incorrect nonce validation on the 'save_account_details' function. This makes it possible for unauthenticated attackers to edit the name, email address, and password of an administrator account via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

Property Hive <= 2.0.19 carries this weakness at save_account_details, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Property Hive the fix is 2.0.20: builds <= 2.0.19 are affected, anything from 2.0.20 onward is not.

Remediation

Update to version 2.0.20, 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. None of that substitutes for the fix: Property Hive 2.0.20 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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