Security readout for executives and security teams
Plain-English summary
An unauthenticated attacker could take over an unconfirmed WordPress account, potentially including an administrator, on specifically configured MyHome sites. The attack can produce a valid login cookie without the victim’s involvement. Compromise could expose site data, allow content or configuration changes, and provide administrative control.
Executive priority
Treat affected, matching configurations as an immediate remediation priority, especially where unconfirmed administrator accounts exist. Rapidly inventory sites, reduce exposure through configuration changes, and follow confirmed vendor guidance for updating.
Technical view
MyHome Core through version 4.4.5 lacks authorization in the send_link() AJAX handler and inadequately validates activation tokens in activate(). An unauthenticated attacker can generate a token for an unconfirmed account and receive its authentication cookie. Exploitation depends on legacy/WPBakery mode, frontend registration with email confirmation, and absence of the myhome_agent_confirmed user metadata.
Likely exposure
Exposure is limited to WordPress installations running MyHome Core 4.4.5 or earlier with legacy/WPBakery mode, frontend registration, and confirmation email enabled. A target account must also remain unconfirmed. Sites using other configurations are not shown as exploitable by the supplied evidence.
Exploitation context
The vulnerability is remotely reachable, requires no privileges or user interaction, and has a CVSS 3.1 score of 9.8. The supplied sources do not establish active exploitation, and the CVE is not listed as KEV.
Researcher notes
The vulnerable path combines missing AJAX authorization with improper activation-token validation. All stated prerequisites matter when assessing practical exposure. The bundle does not name a patched version, vendor mitigation, public proof of concept, or observed attacks; those points should remain unconfirmed pending updated guidance.
Mitigation direction
- Identify and prioritize MyHome Core installations running version 4.4.5 or earlier.
- Check vendor and Wordfence guidance for a fixed release, then update promptly when confirmed.
- Disable frontend registration or email confirmation temporarily if business operations permit.
- Move away from legacy/WPBakery mode where operationally feasible.
- Review and secure unconfirmed privileged accounts until remediation is complete.
Validation and detection
- Confirm the installed MyHome Core version on every WordPress site.
- Verify whether legacy/WPBakery mode is enabled.
- Check whether frontend registration and confirmation email are enabled together.
- Identify unconfirmed accounts, especially administrators, lacking myhome_agent_confirmed metadata.
- Review available logs for unexpected activation requests or logins involving unconfirmed accounts.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-289: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-15980 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9WordfenceVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineWordfence
Vendor Notified
- Source timelineWordfence
Disclosed
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/c458e018-5901-4917-9847-35f07646e068?source=cveCVE reference, Wordfence
- https://themeforest.net/item/myhome-real-estate-wordpress-theme/19508653CVE reference, Wordfence
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE mapping pending import
This CVE carries a CWE mapping that will resolve to a full Glexia CWE intelligence page after the official CWE import is complete.