WordPress security changelog
HIGH CVE-2024-8490 Analyzed

PropertyHive: Cross-site request forgery

PropertyHive is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.

CVE / CNA score 8.8 CVSS 3.1 · security@wordfence.com
NVD score 6.5 CVSS 3.1 · nvd@nist.gov
Component
PropertyHive
Plugin slug
propertyhive
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Sep 17, 2024
Weakness
CWE-352 — Cross-Site Request Forgery (CSRF)

This CVE was published Sep 17, 2024 and is one of 19 known issues for this plugin.

Update, patch or deactivate.

Update PropertyHive to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

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.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

NVD vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Primary and upstream sources