CVE-2026-46620: CWE-285: Improper Authorization in e107inc e107
e107 CMS versions prior to 2.3.5 have an improper authorization vulnerability related to CSRF token validation on comment moderation actions. The session_handler::check() function only validates CSRF tokens if one is present, skipping validation entirely if no token is provided. This allows unauthorized state-changing requests to potentially succeed. The vulnerability is fixed in version 2.3.5. The CVSS score is 6.5, indicating a medium severity level.
AI Analysis
Technical Summary
The e107 content management system before version 2.3.5 improperly enforces CSRF token validation during comment moderation. Specifically, the session_handler::check() method does not require a CSRF token on every state-changing request; it only validates the token if one is present. If no token is included in the request, the validation check is bypassed, leading to improper authorization (CWE-285) and cross-site request forgery (CWE-352) vulnerabilities. This flaw allows attackers to perform unauthorized comment moderation actions. The issue is addressed in e107 version 2.3.5.
Potential Impact
Successful exploitation allows an attacker to perform unauthorized comment moderation actions without proper CSRF token validation. This can lead to unauthorized modification of comments, impacting the integrity of content management. There is no indication of confidentiality or availability impact. The vulnerability is rated medium severity with a CVSS score of 6.5.
Mitigation Recommendations
Upgrade e107 CMS to version 2.3.5 or later, where this vulnerability is fixed. Since the vendor advisory confirms the fix in 2.3.5, applying this official update is the recommended remediation. No other mitigation guidance is provided or necessary.
CVE-2026-46620: CWE-285: Improper Authorization in e107inc e107
Description
e107 CMS versions prior to 2.3.5 have an improper authorization vulnerability related to CSRF token validation on comment moderation actions. The session_handler::check() function only validates CSRF tokens if one is present, skipping validation entirely if no token is provided. This allows unauthorized state-changing requests to potentially succeed. The vulnerability is fixed in version 2.3.5. The CVSS score is 6.5, indicating a medium severity level.
CVSS v3.1
Score 6.5medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The e107 content management system before version 2.3.5 improperly enforces CSRF token validation during comment moderation. Specifically, the session_handler::check() method does not require a CSRF token on every state-changing request; it only validates the token if one is present. If no token is included in the request, the validation check is bypassed, leading to improper authorization (CWE-285) and cross-site request forgery (CWE-352) vulnerabilities. This flaw allows attackers to perform unauthorized comment moderation actions. The issue is addressed in e107 version 2.3.5.
Potential Impact
Successful exploitation allows an attacker to perform unauthorized comment moderation actions without proper CSRF token validation. This can lead to unauthorized modification of comments, impacting the integrity of content management. There is no indication of confidentiality or availability impact. The vulnerability is rated medium severity with a CVSS score of 6.5.
Mitigation Recommendations
Upgrade e107 CMS to version 2.3.5 or later, where this vulnerability is fixed. Since the vendor advisory confirms the fix in 2.3.5, applying this official update is the recommended remediation. No other mitigation guidance is provided or necessary.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-15T19:34:14.012Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a15c089891d628fdc570d25
Added to database: 05/26/2026, 15:47:21 UTC
Last enriched: 06/02/2026, 21:15:16 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 65
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.