---
id: "CVE-2026-109401"
kind: "vulnerability"
aliases: ["CVE-2026-109401"]
title: "WP Mail Logging WordPress plugin leaks other users' mail logs via wildcard"
severity: "low"
cvss: 2.7
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "self-hosted", "wordpress", "wp-mail-logging"]
not_affected_if: ["no-admin-users", "patched-version", "plugin-not-installed"]
published_at: "2026-10-16T07:17:09+00:00"
first_seen_at: "2026-10-23T21:57:12+00:00"
updated_at: "2026-10-25T04:48:10+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-109401", "first_seen_at": "2026-10-23T21:57:12+00:00"}]
---

# WP Mail Logging WordPress plugin leaks other users' mail logs via wildcard

The WP Mail Logging plugin up to and including 1.17.0 mishandles the email_address parameter in its privacy export, so a LIKE wildcard in an address matches other users' logged mail. An authenticated administrator-level attacker can extract those rows, including recipient addresses, subjects, message bodies and URLs.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed version of WP Mail Logging in the WordPress plugins screen or `wp plugin get wp-mail-logging --field=version`
- Confirm whether the plugin is active with `wp plugin is-active wp-mail-logging`

## Fix

- Update WP Mail Logging to a version later than `1.17.0`; the fixed version is unknown from the sources
- Until patched, deactivate the plugin or limit who can process personal-data export requests

## Timeline

- 2026-10-23T21:57:12+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-109401

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_