CVE-2024-29923

7.1 HIGH

📋 TL;DR

This vulnerability allows attackers to inject malicious scripts into web pages generated by the PropertyHive WordPress plugin. When users visit a specially crafted URL, the script executes in their browser, potentially stealing session cookies or performing unauthorized actions. All WordPress sites using PropertyHive versions up to 2.0.8 are affected.

💻 Affected Systems

Products:
  • PropertyHive WordPress Plugin
Versions: n/a through 2.0.8
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: All WordPress installations with PropertyHive plugin enabled are vulnerable by default.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator session cookies, take over WordPress sites, deface websites, or redirect users to malicious sites.

🟠

Likely Case

Attackers steal user session cookies or credentials, perform unauthorized actions on behalf of users, or redirect to phishing pages.

🟢

If Mitigated

With proper input validation and output encoding, the XSS payload would be neutralized before execution.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Reflected XSS vulnerabilities are commonly exploited and require minimal technical skill.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.0.9 or later

Vendor Advisory: https://patchstack.com/database/vulnerability/propertyhive/wordpress-propertyhive-plugin-2-0-8-reflected-cross-site-scripting-xss-vulnerability

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find PropertyHive and click 'Update Now'. 4. Verify version is 2.0.9 or higher.

🔧 Temporary Workarounds

Disable PropertyHive Plugin

all

Temporarily disable the vulnerable plugin until patched.

wp plugin deactivate propertyhive

Web Application Firewall (WAF)

all

Deploy WAF rules to block XSS payloads in URLs.

🧯 If You Can't Patch

  • Implement Content Security Policy (CSP) headers to restrict script execution
  • Use browser security features like HttpOnly and Secure flags for cookies

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel > Plugins > PropertyHive version. If version is 2.0.8 or lower, you are vulnerable.

Check Version:

wp plugin get propertyhive --field=version

Verify Fix Applied:

After updating, verify PropertyHive version is 2.0.9 or higher in WordPress admin panel.

📡 Detection & Monitoring

Log Indicators:

  • Unusual long URLs with script tags in access logs
  • Multiple failed requests to PropertyHive endpoints

Network Indicators:

  • HTTP requests containing <script> tags in query parameters
  • Unusual redirects from PropertyHive pages

SIEM Query:

source="web_access_logs" AND url="*propertyhive*" AND (url="*<script>*" OR url="*javascript:*")

🔗 References

📤 Share & Export