CVE-2026-123417: Check & Log Email: stored XSS via comment parameter
MEDIUMThe Check & Log Email WordPress plugin (versions up to 2.0.17) contains a stored cross-site scripting flaw where an unauthenticated attacker can plant script content through the 'comment' parameter, which later executes in the wp-admin origin. This is a general-purpose WordPress email-logging plugin with no meaningful AI/ML footprint, so the AI-specific blast radius is minimal; exposure only matters if the same WordPress site fronts an AI product, ML documentation portal, or model-gated marketing and customer site. Urgency is low-to-moderate: it is not in CISA KEV, no public exploit or Nuclei template is known, EPSS is not yet available, and exploitation requires an administrator to open a log entry and click a planted link in the Preview panel. Update to a version later than 2.0.17 that includes the fix in the referenced changeset, and train administrators not to click links inside email log previews.
What is the risk?
Medium (CVSS 6.1, AV:N/AC:L/PR:N/UI:R/S:C). Exploitation is network-reachable and needs no authentication, but it needs two administrator actions (opening the log entry and clicking the planted anchor), so the attacker cannot trigger it alone. The changed scope means script runs in the wp-admin origin and can affect admin-level actions. No known active exploitation, KEV listing, public exploit or scanner template. AI/ML-specific risk is low and indirect, relevant only where WordPress hosts or administers AI-related web properties.
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| Check & Log Email – Easy Email Testing & Mail logging | — | — | No patch |
Do you use Check & Log Email – Easy Email Testing & Mail logging? You're affected.
How severe is it?
What is the attack surface?
What should I do?
1 step1) Upgrade Check & Log Email to the first release after 2.0.17 that includes the fix (see the plugins.trac.wordpress.org changeset 3759858). 2) If patching is not immediately possible, deactivate the plugin or disable email logging and restrict access to the log page. 3) Instruct administrators not to click links or hover tooltips in email log Preview panels. 4) Review existing log entries for injected HTML or script in comment fields and purge suspicious entries. 5) Deploy a WAF rule to block script and HTML payloads in the 'comment' parameter on the public endpoints. 6) Enforce a strict Content-Security-Policy on wp-admin and use HttpOnly, SameSite cookies, and MFA for administrator accounts. 7) Monitor for new admin users or unexpected option and plugin changes.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-123417?
The Check & Log Email WordPress plugin (versions up to 2.0.17) contains a stored cross-site scripting flaw where an unauthenticated attacker can plant script content through the 'comment' parameter, which later executes in the wp-admin origin. This is a general-purpose WordPress email-logging plugin with no meaningful AI/ML footprint, so the AI-specific blast radius is minimal; exposure only matters if the same WordPress site fronts an AI product, ML documentation portal, or model-gated marketing and customer site. Urgency is low-to-moderate: it is not in CISA KEV, no public exploit or Nuclei template is known, EPSS is not yet available, and exploitation requires an administrator to open a log entry and click a planted link in the Preview panel. Update to a version later than 2.0.17 that includes the fix in the referenced changeset, and train administrators not to click links inside email log previews.
Is CVE-2026-123417 actively exploited?
No confirmed active exploitation of CVE-2026-123417 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-123417?
1) Upgrade Check & Log Email to the first release after 2.0.17 that includes the fix (see the plugins.trac.wordpress.org changeset 3759858). 2) If patching is not immediately possible, deactivate the plugin or disable email logging and restrict access to the log page. 3) Instruct administrators not to click links or hover tooltips in email log Preview panels. 4) Review existing log entries for injected HTML or script in comment fields and purge suspicious entries. 5) Deploy a WAF rule to block script and HTML payloads in the 'comment' parameter on the public endpoints. 6) Enforce a strict Content-Security-Policy on wp-admin and use HttpOnly, SameSite cookies, and MFA for administrator accounts. 7) Monitor for new admin users or unexpected option and plugin changes.
What systems are affected by CVE-2026-123417?
This vulnerability affects the following AI/ML architecture patterns: WordPress-hosted AI product and documentation sites, ML web portals administered via WordPress.
What is the CVSS score for CVE-2026-123417?
CVE-2026-123417 has a CVSS v3.1 base score of 6.1 (MEDIUM).
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0011.003Malicious LinkAML.T0049Exploit Public-Facing ApplicationCompliance Controls Affected
What are the technical details?
Original Advisory
The Check & Log Email – Easy Email Testing & Mail logging plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' 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. Successful exploitation requires an administrator to open the relevant log entry and click the planted anchor link in the Preview panel, at which point the ThickBox gadget parses the title attribute as live HTML in the wp-admin origin. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.
Exploitation Scenario
An attacker submits a request containing an anchor tag with an HTML-laden title attribute in the 'comment' parameter, which the plugin stores in its email log without sanitization. Later an administrator of a WordPress site that hosts an AI product's marketing or docs pages opens that log entry and clicks the planted link in the Preview panel. The ThickBox gadget parses the title attribute as live HTML, running the attacker's JavaScript in the wp-admin origin. The script creates a new administrator account or steals session tokens, giving the attacker control of the site and a foothold for defacement or phishing against the organization's AI customers.
Weaknesses (CWE)
CWE-79 — Improper Neutralization of Input During Web Page Generation: The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
- [Architecture and Design] Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. Examples of libraries and frameworks that make it easier to generate properly encoded output include Microsoft's Anti-XSS library, the OWASP ESAPI Encoding module, and Apache Wicket.
- [Implementation, Architecture and Design] Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies. For any data that will be output to another web page, especially any data that was received from external inputs, use the appropriate encoding on all non-alphanumeric characters. Parts of the same output document may require different encodings, which will vary depending on whether the output is in the: etc. Note that HTML Entity Encoding is only appropriate for the HTML body. Consult the XSS Prevention Cheat Sheet [REF-724] for more details on the types of encoding and escaping that are needed. HTML body Element attributes (such as src="XYZ") URIs JavaScript sections Casca
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NReferences
- plugins.trac.wordpress.org/browser/check-email/tags/2.0.17/include/Core/Check_Email_Logger.php
- plugins.trac.wordpress.org/browser/check-email/tags/2.0.17/include/Core/Request/Check_Email_Log_List_Action.php
- plugins.trac.wordpress.org/browser/check-email/tags/2.0.17/include/Core/Request/Check_Email_Log_List_Action.php
- plugins.trac.wordpress.org/browser/check-email/tags/2.0.17/include/Core/UI/Page/Check_Email_Log_List_Page.php
- plugins.trac.wordpress.org/changeset/3759858/check-email/trunk/include/Core/Request/Check_Email_Log_List_Action.php
- wordfence.com/threat-intel/vulnerabilities/id/e6bb1e92-fa20-41e2-9793-094d579d9abf
Timeline
Related Vulnerabilities
CVE-2026-274959.9n8n: Code Injection enables RCE
Same attack type: Social EngineeringCVE-2026-275779.9n8n: Code Injection enables RCE
Same attack type: Social EngineeringCVE-2026-284749.8OpenClaw Nextcloud Talk: allowlist bypass via display name
Same attack type: Social EngineeringCVE-2026-860449.6JupyterLab Desktop: open redirect leaks token, enables RCE
Same attack type: Social EngineeringCVE-2026-120489.3pgAdmin 4: Stored XSS enables full browser session hijack
Same attack type: Social Engineering