CVE-2026-5306

Check & Log Email – Easy Email Testing & Mail logging < 2.0.13 - Unauthenticated Stored Cross-Site Scripting

highImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
7.2
CVSS Score
7.2
CVSS Score
high
Severity
2.0.13
Patched in
3d
Time to patch

Description

The Check & Log Email – Easy Email Testing & Mail logging plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to 2.0.13 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.

CVSS Vector Breakdown

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Low
Confidentiality
Low
Integrity
None
Availability

Technical Details

Affected versions<2.0.13
PublishedApril 28, 2026
Last updatedApril 30, 2026
Affected plugincheck-email

What Changed in the Fix

Changes introduced in v2.0.13

Loading patch diff...

Source Code

WordPress.org SVN
Research Plan
Unverified

subject` or `message` column rendering. * **Payload**: `<img src=x onerror=alert(1)>`. * **Vector**: `wp-login.php?action=lostpassword`. * Actually, let's look at `include/Core/UI/Page/Check_Email_Analyzer.php` one more time. * It's a "Free tool". * It might have a pub…

Show full research plan

subjectormessagecolumn rendering. * **Payload**:. * **Vector**: wp-login.php?action=lostpassword`.

*   Actually, let's look at `include/Core/UI/Page/Check_Email_Analyzer.php` one more time.
*   It's a "Free tool".
*   It might have a public-facing page or a way to trigger analysis.
*   But the "Email Log" is the core feature.

*   I will use the "Lost Password" vector as the primary example, as it's the most reliable way to inject into an email log without needing a plugin-specific public endpoint.

*Wait, one more check*:
The description says: "inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page."
This sounds like it could be a public page.
Does this plugin create any public pages?
Not normally. It's an admin tool.
So the victim is the **Admin**.

*   1.  Vulnerability Summary (Stored XSS in Logs).
*   2.  Attack Vector (Lost Password trigger).
*   3.  Code Flow (wp_mail -> Logger -> DB -> Admin Page).
*   4.  Nonce Acquisition (None needed for Lost Password).
*   5.  Exploitation Strategy (Step-

Check if your site is affected.

Run a free security audit to detect vulnerable plugins, outdated versions, and misconfigurations.