CVE-2026-46620 e107: CSRF in comment.php moderation endpoints via token-optional validation in session_handler::check()
Attackers can bypass CSRF protection on comment moderation endpoints in e107 CMS, potentially performing unauthorized actions.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-46620?
CVE-2026-46620 is a medium-severity vulnerability in e107inc e107, published on 26 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
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.
Which versions are affected by CVE-2026-46620?
How do I fix CVE-2026-46620?
No fix has been published for CVE-2026-46620 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-46620 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46620 exists.
Sources
Also known as GHSA-m4hh-m278-jwg5.