CVE-2026-116530: Check & Log Email <= 2.0.17 - Unauthenticated Stored Cross-Site Scripting via 'checkmail-encode' Shortcode via Comment Author Name

Published Nov 18, 2026
·
Updated

The Check & Log Email – Easy Email Testing & Mail logging plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'author' parameter in all versions up to, and including, 2.0.17 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires an administrator to approve the comment carrying the shortcode payload, and the target page must render the core Latest Comments block, which passes comment author names through doshortcode via thecontent.

Affected Software

1 affected component
Check & Log Email Check & Log Email<=2.0.17

Event History

Nov 18, 2026
CVE Published
via MITRE·11:30 AM
Data Sourced
via MITRE·11:30 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which sites are exposed to this issue?

WordPress sites using Check & Log Email version 2.0.17 or earlier are affected only where a page renders the core Latest Comments block. The vulnerable path relies on comment author names being passed through do_shortcode via the page content.

2

What must an attacker do to trigger the stored script execution?

An unauthenticated attacker must submit a comment with a crafted author name containing a checkmail-encode shortcode payload. An administrator must approve that comment, and a user must then access a page that renders the core Latest Comments block.

3

Are sites with comment moderation protected from immediate exploitation?

Comment moderation prevents the payload from being displayed until an administrator approves the malicious comment. It does not remove the risk once the comment is approved and displayed through the affected block.

4

How can I check whether my site may already be affected?

Review approved comments for suspicious shortcode content in author names, particularly checkmail-encode payloads. Also identify pages using the core Latest Comments block, since those pages are required for the described execution path.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203