dbcve.org
PropertyhiveWordPress extension · Wp Property Hive

CVE-2024-35701

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-08
Fix available
A fix is available. Upgrade to 2.0.14 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in PropertyHive allows Stored XSS.This issue affects PropertyHive: from n/a through 2.0.13.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

PropertyHive WordPress plugin versions through 2.0.13 contains a Stored XSS vulnerability where user-supplied input is not properly sanitized before being rendered in web pages, allowing authenticated attackers to inject malicious JavaScript that executes when other users view the affected content.

MitigationUpdate PropertyHive to version 2.0.14 or later when available. Until then, implement output escaping on all user input fields and review admin access permissions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PropertyhiveWordPress extension
Affected:< 2.0.14

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify PropertyHive plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'PropertyHive' or 'Wp Property Hive Propertyhive' in the list
    Affected if Plugin is present and active in the WordPress installation
  2. Check installed version number
    In Plugins list, find the version number displayed under the PropertyHive plugin name, or check plugin file header in wp-content/plugins/propertyhive/propertyhive.php
    Affected if Version number is less than 2.0.14 (for example 2.0.13, 2.0.12, etc.)
  3. Confirm authenticated access exists
    Review user roles and capabilities on the site - check if any user role other than Administrator has access to submit or edit property listing content via PropertyHive
    Affected if Non-admin users have permission to create or edit property/listing content through PropertyHive forms
  4. Identify user input fields in PropertyHive
    Navigate to PropertyHive add/edit forms (typically under Properties menu) and identify fields that accept user-supplied text input such as property titles, descriptions, addresses, or agent notes
    Affected if Text input fields exist that accept user content and are stored in the database
  5. Check if output escaping is implemented
    Inspect the plugin code (propertyhive.php and related template files) for use of esc_html__, esc_attr__, or similar escaping functions when rendering stored PropertyHive data in frontend pages
    Affected if Stored property data is displayed without proper escaping functions on the frontend

The environment is affected if PropertyHive plugin version is below 2.0.14 AND authenticated users can submit content that gets rendered without sanitization on web pages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.0.14 or later
Fixed in 2.0.14
Interim mitigation

Update PropertyHive to version 2.0.14 or later when available. Until then, implement output escaping on all user input fields and review admin access permissions.

Recommended fix High confidence

PropertyHive version 2.0.14

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find PropertyHive in the plugin list
  4. Check if an update is available (if not, check for manual update)
  5. Update PropertyHive to version 2.0.14 or later
  6. Verify the update was successful by checking the plugins page

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Propertyhive Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-35701 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-35701 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data