CVE-2026-46620: medium-severity vulnerability in e107inc e107
e107: CSRF in comment.php moderation endpoints via token-optional validation in session_handler::check()
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 6.5epss 0.1%
e107 is a content management system (CMS). Prior to 2.3.5, e107 CMS does not properly enforce CSRF token validation on comment moderation actions. The problem comes down to how session_handler::check() handles CSRF tokens. Instead of requiring a token on every state-changing request, it only validates the token if one happens to be present. If there is no token at all, the check is skipped entirely. This vulnerability is fixed in 2.3.5.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Affected products
e107inc · e107Related CVEs — e107inc e107
In the same product, most dangerous first.
CVE-2026-48997HIGHe107: Command Injection via shell expansion in ImageMagick resize destination pathEPSS 0.9%CVE-2026-55573CRITICALe107: Unsafe deserialization in install.php allows unauthenticated RCE via POP chainEPSS 0.7%CVE-2026-55572CRITICALe107: SQL injection in alt_auth plugin (otherdb / e107db backends) via login usernameEPSS 0.5%CVE-2026-57859HIGHe107 Second-Order Code Execution via eval()-Based Deserialization in e_array::unserialize()EPSS 0.5%CVE-2026-43935HIGHe107: Host Header Injection in e107 password reset enables phishingEPSS 0.3%CVE-2026-114407MEDIUMe107 CMS before 2.3.13 Reflected XSS via search.php author ParameterEPSS 0.3%