CVE-2026-109401 smub CVE debrief

Who should care

Defenders responsible for WordPress installations using the WP Mail Logging plugin should assess exposure and prioritize verification and potential remediation. This includes operators managing WordPress environments, vulnerability management teams, security teams, and IT staff responsible for plugin updates and security configurations.

Why it matters

The WP Mail Logging plugin for WordPress is vulnerable to Sensitive Information Exposure, potentially allowing authenticated attackers to extract sensitive information. Defenders should prioritize verifying exposure and assessing the impact in their environments.

• Potential exposure of sensitive information, including recipient addresses, message subjects, and full message bodies
• Possible exploitation by authenticated attackers with administrator-level access and above
• Need for verification of exposure and assessment of impact in WordPress installations using the WP Mail Logging plugin

Technical 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.

Defensive priority

Defenders should prioritize verifying exposure and assessing the impact of this vulnerability in their environments, particularly in WordPress installations using the WP Mail Logging plugin.

Recommended defensive actions

• Verify the version of the WP Mail Logging plugin in use and assess exposure
• Restrict access to the plugin's functionality to prevent unauthorized access
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, CVSS score, and references to the affected code in Query.php and WPML_PrivacyController.php. Defenders should verify the version of the WP Mail Logging plugin in use, assess exposure, and monitor for potential exploitation attempts. The CVE Program record and NVD detail page offer additional information on the vulnerability. To verify exposure, defenders should check for affected product deployments in managed environments and review the WP

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.