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.
References
Configurations
No configuration.
History
27 May 2026, 17:16
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/e107inc/e107/security/advisories/GHSA-m4hh-m278-jwg5 - |
26 May 2026, 16:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-05-26 16:16
Updated : 2026-05-27 17:16
NVD link : CVE-2026-46620
Mitre link : CVE-2026-46620
CVE.ORG link : CVE-2026-46620
JSON object : View
Products Affected
No product.
