Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-46620: CWE-285: Improper Authorization in e107inc e107

0
Medium
VulnerabilityCVE-2026-46620cvecve-2026-46620cwe-285cwe-352
Published: Tue May 26 2026 (05/26/2026, 15:04:32 UTC)
Source: CVE Database V5
Vendor/Project: e107inc
Product: e107

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.

CVSS v3.1

Score 6.5medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 05/26/2026, 16:03:12 UTC

Technical Analysis

The e107 content management system before version 2.3.5 improperly enforces CSRF token validation on comment moderation actions. Specifically, the session_handler::check() method does not require a CSRF token on every state-changing request; it only validates the token if present and skips the check if absent. This flaw leads to improper authorization (CWE-285) and CSRF vulnerability (CWE-352), allowing attackers to perform unauthorized comment moderation actions. The issue is resolved in e107 version 2.3.5.

Potential Impact

Successful exploitation allows an attacker to perform unauthorized comment moderation actions by bypassing CSRF token validation. This impacts the integrity of the CMS content but does not affect confidentiality or availability. There are no known exploits in the wild at this time.

Mitigation Recommendations

Upgrade e107 CMS to version 2.3.5 or later, where this vulnerability is fixed. No other official remediation or temporary fixes are documented. Patch status is not explicitly confirmed beyond the version fix; users should verify with the vendor for the latest guidance.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

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: 5/26/2026, 3:47:21 PM

Last enriched: 5/26/2026, 4:03:12 PM

Last updated: 5/26/2026, 9:52:07 PM

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses