Houzez Property Feed <= 2.5.46 - Authenticated (Administrator+) SQL Injection via 'orderby' Parameter
The Houzez Property Feed plugin for WordPress is vulnerable to SQL Injection via the 'orderby' parameter in all versions up to, and including, 2.5.46 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query in the prepare_items() method of the Houzez_Property_Feed_Admin_Logs_Export_Table (and Houzez_Property_Feed_Admin_Logs_Import_Table) class. The user-controlled $_GET['orderby'] and $_GET['order'] values are filtered only with sanitize_text_field() and then concatenated into the SQL format string before $wpdb->prepare() is called — prepare() only parameterizes the appended LIMIT/OFFSET clause and cannot retroactively secure the already-tainted ORDER BY clause. This makes it possible for authenticated attackers, with Administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Quick answer
Houzez Property Feed should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- *-2.5.46
Fixed versions
- 2.5.47
How to fix it
Houzez Property Feed is affected by CVE-2026-13357, a SQL injection and possible sensitive data exposure issue in versions *-2.5.46. Prioritize exposed production sites and users with elevated permissions first. The recommended remediation is to update to version 2.5.47 or a newer vendor-supported patched release. If immediate patching is not possible, reduce exposure, restrict access to the vulnerable workflow, and monitor logs until the vendor-supported fix is in place.
- Inventory every WordPress site that uses Houzez Property Feed, including production, staging, multisite, customer, and managed environments.
- Confirm the installed plugin or theme version and compare it with versions *-2.5.46 from the linked advisory.
- Apply the remediation: update to version 2.5.47 or a newer vendor-supported patched release.
- If the update cannot be applied immediately, disable Houzez Property Feed, remove unused roles that can reach the vulnerable feature, and restrict the affected admin, REST, shortcode, upload, booking, ecommerce, review, or content workflow.
- Review application, web server, security plugin, WAF, authentication, and administrator activity logs for attempts related to CVE-2026-13357.
- Rotate administrator sessions, API keys, webhook secrets, database credentials, and integration tokens if logs or file/content review suggest compromise.
- Clear application, object, page, CDN, and browser caches after remediation so vulnerable assets, stored payloads, or stale responses are not served.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm Houzez Property Feed is no longer running versions *-2.5.46 and record the patched or mitigated version in the remediation ticket.
- Verify unauthenticated, subscriber, contributor, author, editor, shop manager, booking, vendor, or custom-role users can no longer trigger the affected action.
- Review logs before and after the fix for exploitation attempts, unexpected content changes, suspicious admin actions, or database/file access.
- Rerun a Fixnx scan and any relevant plugin, WAF, or manual regression checks to confirm public exposure is reduced.
- Document the advisory link, affected assets, remediation action, verification evidence, and any cleanup or credential rotation performed.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-13357?
Houzez Property Feed versions listed as affected should be reviewed: *-2.5.46.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.