# CVE-2025-0749: Homey <= 2.4.3 - Limited Authentication Bypass due to Missing Empty Value Check

> Unauthenticated attackers can bypass authentication and log in as the first verified user due to a missing empty value check in the Homey WordPress theme.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 7 Mar 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-vv6r-gfm2-qf53

## What is CVE-2025-0749?

CVE-2025-0749 is a high-severity authentication bypass vulnerability in Fave Themes Homey, published on 7 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Homey theme for WordPress is vulnerable to authentication bypass in versions up to, and including, 2.4.3. This is due to the 'verification_id' value being set to empty, and the not empty check is missing in the dashboard user profile page. This makes it possible for unauthenticated attackers to log in to the first verified user.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2025-0749?


## How do I fix CVE-2025-0749?

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

## Is CVE-2025-0749 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0749 and fix it if it is affected.

What it is: CVE-2025-0749 is a high-severity authentication bypass vulnerability in Fave Themes Homey, published on 7 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-2025-0749 in the wild and no public exploit code.

Affected product: Fave Themes Homey. 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-2025-0749/ (Markdown: https://insights.sbomify.com/CVE-2025-0749/index.md)
```

## Sources

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

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