CVE-2026-109401: Software Security Vulnerability Vulnerability

LOW
Advisory Identifier: GHSA-wv84-f6wm-rwxx
CVSS 2.7
CWE-200
Published
Advisory Summary

CVE-2026-109401 is a LOW (CVSS 2.7) security vulnerability vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-109401 at a Glance

CVE Identifier CVE-2026-109401
GHSA Identifier GHSA-wv84-f6wm-rwxx
Severity LOW
CVSS v3.1 Base Score 2.7
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 2.7

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

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

How to Fix CVE-2026-109401

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-109401, 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-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. 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 WP Mail Logging plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.17.0 via the 'email_address' parameter. This makes it possible for authenticated attackers, with administrator-level access and above, to extract complete logged mail rows belonging to other users — including recipient addresses, message subjects, full message bodies, and any URLs contained therein — whose addresses happen to match the wildcard. Exploitation requires an administrator to process a personal-data export request for the attacker's email address via the standard WordPress privacy workflow, and the attacker's address must contain a LIKE wildcard character (such as an underscore) that matches at least one other user's address in the mail log.

References

Frequently Asked Questions

What is CVE-2026-109401?
CVE-2026-109401 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-109401?
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-109401?
CVE-2026-109401 has a CVSS v3.1 base score of 2.7 (LOW) with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2026-109401?
CVE-2026-109401 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check Maven dependencies for CVE-2026-109401?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-wv84-f6wm-rwxx",
  "modified" : "2026-10-16T09:30:27Z",
  "published" : "2026-10-16T09:30:26Z",
  "aliases" : [ "CVE-2026-109401" ],
  "details" : "The WP Mail Logging plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.17.0 via the 'email_address' parameter. This makes it possible for authenticated attackers, with administrator-level access and above, to extract complete logged mail rows belonging to other users — including recipient addresses, message subjects, full message bodies, and any URLs contained therein — whose addresses happen to match the wildcard. Exploitation requires an administrator to process a personal-data export request for the attacker's email address via the standard WordPress privacy workflow, and the attacker's address must contain a LIKE wildcard character (such as an underscore) that matches at least one other user's address in the mail log.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-109401"
  }, {
    "type" : "WEB",
    "url" : "https://plugins.trac.wordpress.org/browser/wp-mail-logging/tags/1.17.0/lib/vendor/brandonwamboldt/wp-orm/src/Query.php#L399"
  }, {
    "type" : "WEB",
    "url" : "https://plugins.trac.wordpress.org/browser/wp-mail-logging/tags/1.17.0/src/WPML_PrivacyController.php#L76"
  }, {
    "type" : "WEB",
    "url" : "https://plugins.trac.wordpress.org/browser/wp-mail-logging/tags/1.17.0/src/WPML_PrivacyController.php#L82"
  }, {
    "type" : "WEB",
    "url" : "https://plugins.trac.wordpress.org/changeset/3746095/wp-mail-logging/trunk/src/WPML_PrivacyController.php?old=3464813&old_path=wp-mail-logging%2Ftrunk%2Fsrc%2FWPML_PrivacyController.php"
  }, {
    "type" : "WEB",
    "url" : "https://plugins.trac.wordpress.org/changeset?reponame=&new=3746095%40wp-mail-logging%2Ftags%2F1.17.1&old=3705796%40wp-mail-logging%2Ftags%2F1.17.0"
  }, {
    "type" : "WEB",
    "url" : "https://www.wordfence.com/threat-intel/vulnerabilities/id/f2b96f36-090d-4ed3-aa2c-dafa89d255cc?source=cve"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "LOW",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-16T07:17:09Z"
  }
}