CVE-2024-3607
First published: Thu May 02 2024(Updated: )
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
Credit: security@wordfence.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WordPress PropertyHive | <=2.0.12 | |
| wp-property-hive PropertyHive WordPress | <2.0.13 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-3607?
CVE-2024-3607 is considered a critical vulnerability due to its potential for unauthorized data deletion.
How do I fix CVE-2024-3607?
To fix CVE-2024-3607, update the PropertyHive plugin to version 2.0.13 or later.
Who is affected by CVE-2024-3607?
Authenticated users with subscriber-level access and above are affected by CVE-2024-3607.
What function is vulnerable in CVE-2024-3607?
The delete_key_date() function in the PropertyHive plugin is vulnerable in CVE-2024-3607.
What versions of PropertyHive are impacted by CVE-2024-3607?
All versions of the PropertyHive plugin up to and including version 2.0.12 are impacted by CVE-2024-3607.
- agent/weakness
- agent/references
- agent/description
- agent/type
- agent/first-publish-date
- agent/severity
- agent/author
- agent/event
- collector/epss-latest
- source/FIRST
- agent/epss
- collector/mitre-cve
- source/MITRE
- agent/source
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-api
- source/NVD
- agent/last-modified-date
- agent/remedy
- agent/softwarecombine
- agent/tags
- vendor/propertyhive
- canonical/wordpress propertyhive
- vendor/wp-property-hive
- canonical/wp-property-hive propertyhive wordpress