CVE-2025-1327

Homey - Booking and Rentals WordPress Theme <= 2.4.4 - Insecure Direct Object Reference to Authenticated (Subscriber+) Arbitrary User Deletion

2025-05-01 00:00
a00n

Strategic Overview

Status
Patched in 2.4.5
Affected Theme
Homey
Affected Version
<= 2.4.4
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2025-1327
View all Homey vulnerabilities

At a glance

CVE-2025-1327 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Homey WordPress theme, affecting versions <= 2.4.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.4.5; sites on affected versions should update now. Disclosed May 2025, reported by a00n.

Vulnerability Overview

The Homey theme for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.4.4 via the 'homey_delete_user_account' action due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete other user's accounts.

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-639: Authorization Bypass Through User-Controlled Key

Homey <= 2.4.4 carries this weakness at homey_delete_user_account, and reaching it takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Homey the fix is 2.4.5: builds <= 2.4.4 are affected, anything from 2.4.5 onward is not.

Remediation

Update to version 2.4.5, or a newer patched version

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. None of that substitutes for the fix: Homey 2.4.5 closes this, and updating the theme is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-1327https://www.wordfence.com/threat-intel/vulnerabilities/id/38aa649c-e9d3-458b-b567-e2e751aaca00https://nvd.nist.gov/vuln/detail/CVE-2025-1327

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C