CSRF in E107inc E107
CVE-2026-46620
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.
EPSS: 0.001 (3.1th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N.
Affected products
- E107inc E107 — versions < 2.3.5
Weakness classification (CWE)
References
- security-advisories@github.com (x_refsource_CONFIRM)
Frequently asked questions
- What is CVE-2026-46620?
- CVE-2026-46620 is a medium-severity vulnerability in E107inc E107, classified under Improper Authorization. CVSS score: 6.5/10. Published 2026-05-26.
- How severe is CVE-2026-46620?
- Medium severity. CVSS v3 base score is 6.5 out of 10.