{"id":"CVE-2026-109401","revision":"ac29998cd3bf462193ae2d1284a2ad85","records":[{"revision":"ac29998cd3bf462193ae2d1284a2ad85","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2026-109401","aliases":[],"title":"WP Mail Logging <= 1.17.0 - Authenticated (Administrator+) Sensitive Information Exposure in LIKE Wildcard in Personal Data Export Email","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.","state":0,"publishedAt":"2026-10-16T06:41:07.717+00:00","modifiedAt":"2026-10-16T14:21:19.789+00:00","affected":[{"ecosystem":"Vendor product","name":"WP Mail Logging","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"smub\",\n                    \"product\": \"WP Mail Logging\",\n                    \"versions\": [\n                        {\n                            \"version\": \"0\",\n                            \"status\": \"affected\",\n                            \"lessThanOrEqual\": \"1.17.0\",\n                            \"versionType\": \"semver\"\n                        }\n                    ],\n                    \"defaultStatus\": \"unaffected\"\n                }"}],"metrics":[{"system":"CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N","score":2.7,"severity":"LOW"}],"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"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-109401","license":"CVE Program Terms of Use","key":"cve-program:CVE-2026-109401","identifiers":["CVE-2026-109401"]},"retained":false,"historicalAffected":[]}],"coverage":[]}