CVE-2026-93889 wardee CVE debrief

Who should care

Defenders responsible for WordPress installations using the Mail logging – WP Mail Catcher plugin, especially if a separately installed plugin like Contact Form 7 is used, should assess exposure and prioritize verification and potential remediation.

Why it matters

The Mail logging – WP Mail Catcher plugin for WordPress is vulnerable to Stored Cross-Site Scripting via PHPMailer 'wp_mail_failed' Error Message. Defenders should prioritize verifying exposure, especially if a separately installed plugin like Contact Form 7 is used, and consider implementing compensating controls.

• Defenders need to verify exposure of WordPress installations using the Mail logging – WP Mail Catcher plugin.
• Successful exploitation could allow unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
• Remediation priority follows from verifying exposure and assessing the risk of exploitation.

Technical summary

The Mail logging – WP Mail Catcher plugin for WordPress is vulnerable to Stored Cross-Site Scripting via PHPMailer 'wp_mail_failed' Error Message in all versions up to, and including, 2.1.12. This is due to insufficient input sanitization and output escaping. Successful exploitation requires a separately installed plugin, such as Contact Form 7, that passes unauthenticated user-controlled input into mail fields whose content PHPMailer will include in its failure error message.

Defensive priority

Defenders should prioritize verifying exposure of WordPress installations using the Mail logging – WP Mail Catcher plugin, especially if a separately installed plugin like Contact Form 7 is used.

Recommended defensive actions

• Verify exposure of WordPress installations using the Mail logging – WP Mail Catcher plugin, especially if a separately installed plugin like Contact Form 7 is used.
• Check for usage of the affected plugin versions and assess the risk of exploitation.
• Consider implementing compensating controls, such as monitoring for suspicious activity or restricting access to the plugin's functionality.
• Review 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. Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description and CVSS score. However, the corpus does not establish versions beyond 2.1.12, exploitation, impact, or remediation, which require verification from the supplied official sources.

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.