Security readout for executives and security teams
Plain-English summary
CVE-2024-23513 affects the WordPress PropertyHive plugin through version 2.0.5. It is a PHP object injection issue caused by unsafe deserialization. A successful attack could compromise sensitive data or site integrity, but the CVSS vector rates attack complexity as high and the supplied sources do not show active exploitation.
Executive priority
Treat this as a high-priority WordPress plugin exposure check. It does not currently have cited active exploitation, but affected public sites could face confidentiality and integrity compromise if successfully attacked.
Technical view
The vulnerability is CWE-502 deserialization of untrusted data in PropertyHive for WordPress, affecting versions through 2.0.5. CVSS 3.1 is 8.7: network reachable, unauthenticated, no user interaction, high complexity, changed scope, high confidentiality and integrity impact, and no availability impact listed.
Likely exposure
Exposure is limited to WordPress installations running the PropertyHive plugin at version 2.0.5 or earlier. Public-facing real-estate or property websites using this plugin should be prioritized for inventory and version validation.
Exploitation context
The CVE is not listed as KEV in the supplied bundle. No cited source in the bundle provides evidence of active exploitation. Risk remains meaningful because the issue is unauthenticated and network reachable, even though attack complexity is rated high.
Researcher notes
Evidence is sparse in the supplied bundle. The strongest facts are the affected version range, CWE-502 classification, CVSS vector, Patchstack reference, and lack of KEV status. Do not assume exploitability details, gadget chains, or a confirmed fixed version without vendor confirmation.
Mitigation direction
- Identify all WordPress sites using the PropertyHive plugin.
- Upgrade PropertyHive to a version outside the affected range if vendor guidance confirms availability.
- If no safe update is available, disable or remove the plugin where operationally feasible.
- Review Patchstack and vendor guidance before applying production changes.
- Increase monitoring for suspicious requests against affected WordPress sites.
Validation and detection
- Confirm installed PropertyHive versions across production, staging, and backups.
- Verify no internet-facing site runs PropertyHive 2.0.5 or earlier.
- Check vulnerability management records for CVE-2024-23513 coverage.
- Review web and application logs for unusual activity around affected sites.
- Document any temporary compensating controls and remaining exposed systems.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-23513 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N2.25.8Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.7HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.