MyHome Core <= 4.4.5 - Authentication Bypass to Account Takeover via Activation Token
Strategic Overview
- Status
- Patched in 4.4.6
- Affected Plugin
- MyHome Core
- Affected Version
<= 4.4.5- CVSS
- 9.8Critical
- Weakness type
- CWE-289 · Authentication Bypass by Alternate Name
- CVE
CVE-2026-15980
At a glance
CVE-2026-15980 is a critical-severity Authentication Bypass by Alternate Name vulnerability in the MyHome Core WordPress plugin, affecting versions <= 4.4.5. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.4.6; sites on affected versions should update now. Disclosed August 2026, reported by Rafie Muhammad.
Vulnerability Overview
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.
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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-289: Authentication Bypass by Alternate Name
MyHome Core <= 4.4.5 carries this weakness at send_link(), and reaching it takes a caller who can reach the endpoint. Authentication bypass by alternate name means access checks are performed against one form of an identifier while the sensitive operation uses another, so a differently spelled value slips through.
Registering or supplying a variant spelling of a privileged account's identifier is enough to be treated as that account. For MyHome Core the fix is 4.4.6: builds <= 4.4.5 are affected, anything from 4.4.6 onward is not.
Remediation
Update to version 4.4.6, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: MyHome Core 4.4.6 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Other vulnerabilities in MyHome Core
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C