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.
Published: 2026-05-26
Score: 6.5 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability is a flaw in e107 CMS in which comment moderation actions do not enforce CSRF token validation. The session_handler::check() routine only validates a token if one is present; when a token is absent the check is skipped, allowing an attacker to trigger comment approval or rejection requests without user consent. This can result in publication of malicious content or removal of legitimate comments and is classified as a moderate severity issue (CVSS 6.5) associated with CWE‑352 and CWE‑285.

Affected Systems

All installations of e107 CMS prior to version 2.3.5 are affected. The fix is included in release 2.3.5; no other vendors or products are listed.

Risk and Exploitability

With a CVSS score of 6.5 the risk is moderate, but no EPSS score is available and the CVE is not listed in CISA’s KEV catalog. The attack vector is web‑based; an adversary could send a crafted request to the moderation endpoint or lure an authenticated administrator to a malicious site that issues the request. Exploitation requires the victim to be authenticated, but the CSRF bypass removes the need for any additional privileges beyond the target’s authenticated session.

Generated by OpenCVE AI on May 26, 2026 at 16:20 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update e107 CMS to version 2.3.5 or later, which implements proper CSRF token validation.
  • If an upgrade cannot be performed immediately, limit access to comment moderation pages to trusted administrators or temporarily disable those endpoints.
  • Ensure that all state‑changing endpoints enforce CSRF token presence; if the framework does not enforce it automatically, implement an additional check or middleware to require a valid token before processing the request.

Generated by OpenCVE AI on May 26, 2026 at 16:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

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

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-05-26T15:04:32.092Z

Reserved: 2026-05-15T19:34:14.012Z

Link: CVE-2026-46620

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-05-26T16:16:26.130

Modified: 2026-05-26T16:16:26.130

Link: CVE-2026-46620

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-05-26T17:30:10Z

Weaknesses