Skip to content
Fencer Intel
high 7.2

CVE-2026-116530 json

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

published 15h ago modified 12h ago also EUVD-2026-128557

cvss
7.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

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 do_shortcode via the_content.

Is CVE-2026-116530 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
13h ago

CVSS scores

assigned by version score vector
CNA 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Affected products

  • checkemail Check & Log Email – Easy Email Testing & Mail logging

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.