Quick answers
- Is CVE-2026-46620 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-46620 being exploited in the wild.
- How severe is CVE-2026-46620?
- Medium severity, with a CVSS score of 6.5, published 26 May 2026.
- Which products and versions are affected?
- E107inc E107 < 2.3.5.
- Is there a fix for CVE-2026-46620?
- A patch was published on 2026-05-26: Fix released in version 2.3.5 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-46620 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-46620?
- Check whether you run E107inc E107 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Cross-Site Request Forgery (CSRF) vulnerability exists in e107 CMS due to improper token validation in the session_handler::check() function. The root cause is that the system only validates a CSRF token if one is present in the request; if the token is omitted entirely, the validation check is bypassed. An attacker can exploit this by hosting a malicious webpage that sends forged POST requests to the comment.php moderation endpoints (delete and approve modes). If an authenticated administrator or moderator visits the attacker's site, the forged requests will execute in their session context. This allows for the unauthorized modification of comment states in the database. The issue is fixed in version 2.3.5 by enforcing token presence for state-mutating requests.
Affected products
- e107inc e107 < 2.3.5
Timeline
- 2026-05-13: other: Vulnerability discovered by researcher
- 2026-05-18: advisory: GitHub security advisory published
- 2026-05-26: disclosed: CVE published to NVD
- 2026-05-26: patched: Fix released in version 2.3.5