dbcve.org
PropertyhiveWordPress extension · Wp Property Hive

CVE-2024-34381

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-06
Fix available
A fix is available. Upgrade to 2.0.11 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 ('Cross-site Scripting') vulnerability in PropertyHive allows Stored XSS.This issue affects PropertyHive: from n/a through 2.0.10.

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 · moderate confidence

A stored cross-site scripting (XSS) vulnerability exists in PropertyHive plugin versions up to 2.0.10. Authenticated users with low privileges can inject malicious JavaScript payloads through user input fields that are not properly sanitized. When other users view the affected content, the injected script executes in their browsers, potentially allowing session hijacking or credential theft.

MitigationImplement output encoding and input sanitization on all user-supplied data before rendering in HTML context. Validate and escape data at the point of display using context-appropriate encoding functions.

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.11

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
    Access your WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'PropertyHive' or 'Wp Property Hive Propertyhive' in the list of active plugins.
    Affected if The PropertyHive plugin appears in your WordPress plugins list and is activated.
  2. Check the installed version number
    In the Plugins list, find PropertyHive and locate the version number displayed below the plugin name. Alternatively, check the plugin header in /wp-content/plugins/propertyhive/propertyhive.php for the 'Version' tag.
    Affected if The displayed version number is less than 2.0.11 (for example, 2.0.10, 2.0.9, 2.0.8, etc.).
  3. Identify user roles with access to input fields
    Navigate to WordPress Users > Roles or use a role management plugin to examine which roles have permission to create or edit PropertyHive content such as properties, contacts, or applicant records.
    Affected if Low-privilege roles (such as Subscriber, Contributor, or a custom role with limited permissions) have the ability to add or edit PropertyHive content containing user input fields.
  4. Locate unsanitized user input points
    Review the PropertyHive settings and any custom field configurations where users can enter data that gets stored and displayed later. Check forms for property listings, applicant details, or contact information where text input fields accept user-supplied data.
    Affected if User input fields exist in PropertyHive that accept and store text data without visible sanitization indicators or that display raw user input in the frontend/admin interface.

You are affected if PropertyHive version is below 2.0.11 AND your site permits low-privilege authenticated users to submit content through input fields that render unescaped output to other users.

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.11 or later
Fixed in 2.0.11
Interim mitigation

Implement output encoding and input sanitization on all user-supplied data before rendering in HTML context. Validate and escape data at the point of display using context-appropriate encoding functions.

Recommended fix High confidence

PropertyHive version 2.0.11

  1. 1. Create a complete backup of the WordPress site, including database and files
  2. 2. Update PropertyHive plugin to version 2.0.11 or later through WordPress admin dashboard (Plugins > Add New > Upload or directly from the WordPress repository)
  3. 3. Alternatively, update via FTP by downloading version 2.0.11 from the WordPress plugin repository and replacing the existing files
  4. 4. Clear any server-side and CDN caches after updating
  5. 5. Verify the update was successful by checking the plugin version in WordPress admin (Plugins > Installed Plugins)
Caveat Review plugin changelog for any breaking changes between your current version and 2.0.11; test in staging environment first if running older version

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

Fix this in Propertyhive Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-34381 — 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-34381 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