# CVE-2024-11951: Homey Login Register <= 2.4.0 - Unauthenticated Privilege Escalation in homey_register

> Unauthenticated attackers can gain administrator privileges by setting their own role during account registration in the Homey Login Register plugin.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Mar 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-9r9q-wj4f-283m

## What is CVE-2024-11951?

CVE-2024-11951 is a critical vulnerability in Fave Themes Homey Login Register, published on 5 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Homey Login Register plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 2.4.0. This is due to the plugin allowing users who are registering new accounts to set their own role. This makes it possible for unauthenticated attackers to gain elevated privileges by creating an account with the administrator role.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2024-11951?


## How do I fix CVE-2024-11951?

No fix has been published for CVE-2024-11951 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-11951 being exploited?

There is no known exploitation of CVE-2024-11951 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-11951 and fix it if it is affected.

What it is: CVE-2024-11951 is a critical vulnerability in Fave Themes Homey Login Register, published on 5 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-11951 in the wild and no public exploit code.

Affected product: Fave Themes Homey Login Register. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-11951/ (Markdown: https://insights.sbomify.com/CVE-2024-11951/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-11951
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-11951
- OSV: https://osv.dev/vulnerability/CVE-2024-11951

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-11951/
Summaries are generated and may contain mistakes; the official description above is the record.