PropertyhiveWordPress extension · Wp Property Hive
CVE-2024-29923
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in PropertyHive allows Reflected XSS.This issue affects PropertyHive: from n/a through 2.0.8.
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 confidenceReflected XSS vulnerability in PropertyHive plugin allows attackers to inject malicious scripts via unsanitized user input that gets reflected in web pages. The CVSS 6.1 score indicates a network-exploitable issue requiring user interaction.
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
< 2.0.9CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify PropertyHive plugin installation and versionNavigate to WordPress admin > Plugins and locate 'PropertyHive' in the installed plugins list. Note the installed version number displayed below the plugin name.Affected if The plugin is installed and the version number is lower than 2.0.9 (e.g., 2.0.8, 2.0.7, etc.)
-
Identify reflected URL parametersReview your web server logs or use a browser to manually test query string parameters on PropertyHive pages (e.g., search results, property listings). Common reflected XSS parameters include 's', 'search', 'id', or any parameter visible in the URL that gets echoed back in the page HTML.Affected if Any user-supplied URL parameter from PropertyHive is reflected in the page source without HTML encoding (e.g., raw parameter values appearing in page content)
-
Inspect page source for unsanitized outputVisit a PropertyHive page that accepts URL parameters, view the page source (right-click > View Page Source), and search for your parameter values. Check if they appear inside HTML tags (like <a href="..."> or <input value="...">) without being escaped (look for actual parameter text vs. <encoded> entities).Affected if Parameter values from the URL are visible in plain text within HTML elements instead of being converted to HTML entities (e.g., 'test' appears as 'test' rather than '<test>' inside an HTML attribute)
-
Check for missing WordPress escaping functionsIf you have file access, review PHP files in the /wp-content/plugins/propertyhive/ directory, specifically files handling form submissions or search queries. Look for echo or print statements containing $_GET, $_POST, or $_REQUEST variables that lack esc_html(), esc_attr(), or esc_url() wrapping.Affected if User input from $_GET/$_POST/$_REQUEST is directly output to HTML without being passed through WordPress escaping functions like esc_html(), esc_attr(), or wp_kses()
You are affected if the PropertyHive plugin version is below 2.0.9 AND any URL parameters are reflected in PropertyHive pages without proper HTML encoding.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.0.9
Apply proper input validation and output encoding/sanitization (using WordPress escaping functions like esc_html(), esc_attr(), or wp_kses()) on all user-supplied parameters before reflecting them in HTML output.
2.0.9
- 1. Back up your current WordPress installation and database before making any changes
- 2. Navigate to the WordPress admin dashboard for your PropertyHive installation
- 3. Go to Plugins > Installed Plugins and locate the PropertyHive plugin
- 4. Check if an update to version 2.0.9 is available in the plugin repository
- 5. If update is available, click 'Update Now' to upgrade to version 2.0.9
- 6. If no update is available through the WordPress repository, download version 2.0.9 from the official PropertyHive source
- 7. Deactivate and delete the current PropertyHive plugin (backup your configuration first if needed)
- 8. Upload and install version 2.0.9
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Propertyhive
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29923 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-29923 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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