# CVE-2026-15980: MyHome Core <= 4.4.5 - Authentication Bypass to Account Takeover via Activation Token

> Unauthenticated attackers can bypass authentication to take over accounts, including administrators, in the MyHome Core WordPress 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:** 30 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-6hcx-8gm4-gx5h

## What is CVE-2026-15980?

CVE-2026-15980 is a critical authentication bypass vulnerability in TangibleWP MyHome Core, published on 30 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The MyHome Core plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 4.4.5. This is due to missing authorization in the send_link() AJAX handler and improper token validation in the activate() function. This makes it possible for unauthenticated attackers to generate an activation token for an unconfirmed user account and obtain a valid authentication cookie for that account, including administrators. Successful exploitation requires the MyHome theme to be configured in legacy/WPBakery mode with frontend registration and confirmation email enabled, and the target account must not already have the myhome_agent_confirmed user meta set.

Weakness: CWE-289 (Authentication Bypass by Alternate Name)

## Which versions are affected by CVE-2026-15980?


## How do I fix CVE-2026-15980?

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

## Is CVE-2026-15980 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15980 and fix it if it is affected.

What it is: CVE-2026-15980 is a critical authentication bypass vulnerability in TangibleWP MyHome Core, published on 30 Aug 2026. 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-2026-15980 in the wild and no public exploit code.

Affected product: TangibleWP MyHome Core. 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-2026-15980/ (Markdown: https://insights.sbomify.com/CVE-2026-15980/index.md)
```

## Sources

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

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