6.5
MEDIUM CVSS 3.1
CVE-2026-46620
e107: CSRF in comment.php moderation endpoints via token-optional validation in session_handler::check()
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.

INFO

Published Date :

May 26, 2026, 4:16 p.m.

Last Modified :

May 26, 2026, 7:29 p.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2026-46620 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 MEDIUM [email protected]
Solution
Update e107 CMS to version 2.3.5 to fix CSRF token validation.
  • Update e107 CMS to version 2.3.5.
  • Verify CSRF token validation is enforced.
  • Review session handler for token validation logic.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-46620.

URL Resource
https://github.com/e107inc/e107/security/advisories/GHSA-m4hh-m278-jwg5
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-46620 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-46620 weaknesses.

CAPEC-1: Accessing Functionality Not Properly Constrained by ACLs Accessing Functionality Not Properly Constrained by ACLs CAPEC-5: Blue Boxing Blue Boxing CAPEC-13: Subverting Environment Variable Values Subverting Environment Variable Values CAPEC-17: Using Malicious Files Using Malicious Files CAPEC-39: Manipulating Opaque Client-based Data Tokens Manipulating Opaque Client-based Data Tokens CAPEC-45: Buffer Overflow via Symbolic Links Buffer Overflow via Symbolic Links CAPEC-51: Poison Web Service Registry Poison Web Service Registry CAPEC-59: Session Credential Falsification through Prediction Session Credential Falsification through Prediction CAPEC-60: Reusing Session IDs (aka Session Replay) Reusing Session IDs (aka Session Replay) CAPEC-76: Manipulating Web Input to File System Calls Manipulating Web Input to File System Calls CAPEC-77: Manipulating User-Controlled Variables Manipulating User-Controlled Variables CAPEC-87: Forceful Browsing Forceful Browsing CAPEC-104: Cross Zone Scripting Cross Zone Scripting CAPEC-127: Directory Indexing Directory Indexing CAPEC-402: Bypassing ATA Password Security Bypassing ATA Password Security CAPEC-647: Collect Data from Registries Collect Data from Registries CAPEC-668: Key Negotiation of Bluetooth Attack (KNOB) Key Negotiation of Bluetooth Attack (KNOB) CAPEC-62: Cross Site Request Forgery Cross Site Request Forgery CAPEC-111: JSON Hijacking (aka JavaScript Hijacking) JSON Hijacking (aka JavaScript Hijacking) CAPEC-462: Cross-Domain Search Timing Cross-Domain Search Timing CAPEC-467: Cross Site Identification Cross Site Identification

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-46620 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-46620 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    May. 26, 2026

    Action Type Old Value New Value
    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.
    Added CVSS V3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
    Added CWE CWE-352
    Added CWE CWE-285
    Added Reference https://github.com/e107inc/e107/security/advisories/GHSA-m4hh-m278-jwg5
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.