PropertyhiveWordPress extension · Wp Property Hive
CVE-2023-22706
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.48 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 · high confidenceThis is an unauthenticated reflected cross-site scripting (XSS) vulnerability in the PropertyHive WordPress plugin affecting versions 1.5.48 and below. Attackers can inject malicious JavaScript through vulnerable parameters that are reflected back to users without proper sanitization or output encoding.
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.48CVSS 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 is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'PropertyHive' or check the plugin files in /wp-content/plugins/propertyhive/ for a version fileAffected if PropertyHive plugin is present on the WordPress site
-
Determine the installed version of PropertyHiveCheck the plugin version listed in the WordPress plugins admin page, or read the main plugin file header in /wp-content/plugins/propertyhive/propertyhive.php for the 'Version' tagAffected if The version number is 1.5.48 or lower
-
Confirm the plugin is activeIn WordPress admin > Plugins, verify that PropertyHive shows as 'Active'Affected if The plugin is active and accessible to unauthenticated users
-
Identify accessible PropertyHive endpoints that reflect user inputReview publicly accessible PropertyHive pages (property search, enquiry forms, frontend submissions) and test for reflected parameters in the URL query stringAffected if The site uses frontend PropertyHive features that reflect URL parameters back to the user without sanitization
If PropertyHive plugin version is 1.5.48 or lower and the site has active frontend endpoints that reflect URL parameters, the environment is likely affected by this 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.
From vendor dataUpdate PropertyHive plugin to version 1.5.49 or later to patch the XSS vulnerability. Until updated, sanitize user inputs and implement Content Security Policy headers as a temporary workaround.
Fix this in Propertyhive
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22706 — 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-22706 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