HomeWordPress vulnerabilitiesProperty Hive
Property Hive vulnerabilities
Property Hive has 4 known vulnerabilities in this database. The most recent published record is dated 8 Jan 2025.
- Known vulnerabilities
- 4
- Active installs
- 3,000+
- Latest version
- 2.4.0
- Last updated
- 23 Sep 2026
- Most recent
- 8 Jan 2025
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2024-12585 | Medium 6.1 | Before 2.1.1 | Fixed in 2.1.1 | 8 Jan 2025 |
| Cross-site request forgery (CSRF) CVE-2024-8490 | High 8.8 | Before 2.0.20 | Fixed in 2.0.20 | 17 Sep 2024 |
| Broken access control CVE-2024-3607 | Medium 4.3 | Before 2.0.13 | Fixed in 2.0.13 | 2 May 2024 |
| Cross-site scripting (XSS) CVE-2018-6465 | Medium 6.1 | Before 1.4.15 | Fixed in 1.4.15 | 31 Jan 2018 |
Read the published descriptions
- CVE-2024-12585, 8 Jan 2025
- The Property Hive WordPress plugin before 2.1.1 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin. CVE record
- CVE-2024-8490, 17 Sep 2024
- 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 record
- CVE-2024-3607, 2 May 2024
- The PropertyHive plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the delete_key_date() function in all versions up to, and including, 2.0.12. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary posts CVE record
- CVE-2018-6465, 31 Jan 2018
- The PropertyHive plugin before 1.4.15 for WordPress has XSS via the body parameter to includes/admin/views/html-preview-applicant-matches-email.php. CVE record
What to do if you run Property Hive
If you run Property Hive, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Property Hive vulnerabilities
Free. We email you when a new vulnerability is published for Property Hive, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.