CVE-2026-109401 json
WP Mail Logging <= 1.17.0 - Authenticated (Administrator+) Sensitive Information Exposure in LIKE Wildcard in Personal Data Export Email
published 24d ago modified 24d ago also EUVD-2026-102800
- cvss
- 2.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 25%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-109401 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 24d ago
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 2.7 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N |
Affected products
- smub WP Mail Logging
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/f2b96f36-090d-4ed3-aa2c-dafa89d255cc?source=cve
- plugins.trac.wordpress.org /browser/wp-mail-logging/tags/1.17.0/lib/vendor/brandonwamboldt/wp-orm/src/Query.php#L399
- plugins.trac.wordpress.org /browser/wp-mail-logging/tags/1.17.0/src/WPML_PrivacyController.php#L76
- plugins.trac.wordpress.org /browser/wp-mail-logging/tags/1.17.0/src/WPML_PrivacyController.php#L82
- plugins.trac.wordpress.org /changeset/3746095/wp-mail-logging/trunk/src/WPML_PrivacyController.php?old=3464813&old_path=wp-mail-logging%2
- plugins.trac.wordpress.org /changeset?reponame=&new=3746095%40wp-mail-logging%2Ftags%2F1.17.1&old=3705796%40wp-mail-logging%2Ftags%2F1.17
Sources
- CVE List CVE-2026-109401
- NVD CVE-2026-109401
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.