PropertyhiveWordPress extension · Wp Property Hive
CVE-2023-29172
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in PropertyHive plugin <= 1.5.46 versions.
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 confidenceAn unauthenticated reflected cross-site scripting (XSS) vulnerability exists in the PropertyHive WordPress plugin versions 1.5.46 and below. The vulnerability allows attackers to inject malicious JavaScript code through unsanitized user input that is reflected back in the application's response.
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
< 1.5.47CVSS 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.
-
Check if PropertyHive plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'PropertyHive' or 'Property Hive' in the listAffected if PropertyHive plugin is present in the WordPress installation
-
Verify the installed version of PropertyHiveIn the Plugins list, find PropertyHive and view the version number displayed below the plugin name. Compare it to the affected version range: 1.5.46 and below are vulnerableAffected if The installed version is 1.5.46 or lower (less than 1.5.47)
-
Confirm the plugin is activeIn the Plugins list, verify that PropertyHive shows as 'Active' rather than 'Inactive' or 'Deactivated'Affected if The plugin is currently active and running on the site
-
Identify the entry point for user inputReview the PropertyHive plugin settings and public-facing forms where user input is collected (such as property search, contact forms, or enquiry fields). The vulnerability lies in reflected user input that is not sanitized before being outputAffected if The plugin accepts and reflects user-supplied input back to the browser without proper encoding
The environment is affected if PropertyHive plugin version 1.5.46 or lower is installed and active on the WordPress site, as this version contains the unsanitized reflected XSS vulnerability.
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 · scoped1.5.47
Update PropertyHive plugin to version greater than 1.5.46 to include the security patch that properly sanitizes user input and encodes output.
PropertyHive version 1.5.47 or later
- 1. Navigate to the WordPress admin dashboard
- 2. Go to Plugins > Installed Plugins
- 3. Locate the PropertyHive plugin
- 4. Check if an update to version 1.5.47 or newer is available
- 5. If an update is available, click 'Update Now' to upgrade to the fixed version
- 6. After updating, verify the plugin is running version 1.5.47 or newer in the plugins list
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Propertyhive
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29172 — 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-2023-29172 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