CVE-2026-15980: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-6hcx-8gm4-gx5h
Share
CVSS 9.8
CWE-289
Published
Advisory Summary

CVE-2026-15980 is a CRITICAL (CVSS 9.8) security vulnerability vulnerability (CWE-289: Authentication Bypass by Alternate Name) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product performs authentication based on the name of a resource being accessed, or the name of the actor performing the access, but it does not properly check all possible names for that resource or actor.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-15980 at a Glance

CVE Identifier CVE-2026-15980
GHSA Identifier GHSA-6hcx-8gm4-gx5h
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification CWE-289: Authentication Bypass by Alternate Name
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 9.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-15980

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-15980, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-289: Authentication Bypass by Alternate Name, where the product performs authentication based on the name of a resource being accessed, or the name of the actor performing the access, but it does not properly check all possible names for that resource or actor. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-15980 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-15980
themeforest.net/item/myhome-real-es... WEB
https://themeforest.net/item/myhome-real-estate-wordpress-theme/19508653
www.wordfence.com/threat-intel/vulner... WEB
https://www.wordfence.com/threat-intel/vulnerabilities/id/c458e018-5901-4917-9847-35f07646e068?source=cve

Frequently Asked Questions

What is CVE-2026-15980?
CVE-2026-15980 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-289: Authentication Bypass by Alternate Name.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-15980?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-15980?
CVE-2026-15980 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-15980?
CVE-2026-15980 is classified under CWE-289: Authentication Bypass by Alternate Name (The product performs authentication based on the name of a resource being accessed, or the name of the actor performing the access, but it does not properly check all possible names for that resource or actor.).
How can I check Maven dependencies for CVE-2026-15980?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-6hcx-8gm4-gx5h",
  "modified" : "2026-08-30T06:30:21Z",
  "published" : "2026-08-30T06:30:21Z",
  "aliases" : [ "CVE-2026-15980" ],
  "details" : "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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-15980"
  }, {
    "type" : "WEB",
    "url" : "https://themeforest.net/item/myhome-real-estate-wordpress-theme/19508653"
  }, {
    "type" : "WEB",
    "url" : "https://www.wordfence.com/threat-intel/vulnerabilities/id/c458e018-5901-4917-9847-35f07646e068?source=cve"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-289" ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-30T05:16:58Z"
  }
}