No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Wed, 27 May 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 26 May 2026 17:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
E107
E107 e107 |
|
| Vendors & Products |
E107
E107 e107 |
Tue, 26 May 2026 15:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | e107: CSRF in comment.php moderation endpoints via token-optional validation in session_handler::check() | |
| Weaknesses | CWE-285 CWE-352 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-05-27T16:04:41.864Z
Reserved: 2026-05-15T19:34:14.012Z
Link: CVE-2026-46620
Updated: 2026-05-27T16:04:38.565Z
Status : Deferred
Published: 2026-05-26T16:16:26.130
Modified: 2026-05-27T17:16:40.590
Link: CVE-2026-46620
No data.
OpenCVE Enrichment
Updated: 2026-05-26T17:30:10Z