HomeSweet - Real Estate WordPress Theme <= 1.4 - Insecure Direct Object Reference
Strategic Overview
- Status
- Unpatched
- Affected Theme
- HomeSweet - Real Estate WordPress Theme
- Affected Version
<= 1.4- CVSS
- 5.4Medium
- Weakness type
- CWE-284 · Improper Access Control
- CVE
CVE pending
At a glance
This record tracks a medium-severity Improper Access Control vulnerability in the HomeSweet - Real Estate WordPress Theme WordPress theme, affecting versions <= 1.4. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). No fixed release has been reported yet; treat installations running this software as exposed. Disclosed June 2020, reported by R3N0.
Vulnerability Overview
The HomeSweet - Real Estate WordPress Theme is vulnerable to Insecure Direct Object Reference via 'property_id=2769&remove_property_form=' in versions up to, and including, 1.4. This makes it possible for authenticated attackers to delete arbitrary ads within the vulnerable service.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-284: Improper Access Control
Reaching this weakness in HomeSweet - Real Estate WordPress Theme <= 1.4 takes a caller who can reach the endpoint. Improper access control means the code decides what a caller may do using something other than their actual permissions, so the decision can be wrong without any check appearing to be missing.
Whoever can shape the request decides the answer, so the protected action runs for callers the code never meant to allow. No fixed build of this theme is recorded for HomeSweet - Real Estate WordPress Theme yet, so installs running <= 1.4 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C