Unauthorized comment moderation via token-optional CSRF validation
Published May 26, 2026 · Updated May 26, 2026
Cross-site request forgery in e107 before 2.3.5 allows remote attackers to approve or delete comments through a moderator's browser. The comment.php approve and delete handlers execute state changes when session_handler::check() receives no CSRF token because validation runs only when a token is present. Exploitation requires a logged-in administrator or moderator to open an attacker-controlled page, after which arbitrary site comments can be silently approved or deleted.
Summary
What happened
Cross-site request forgery in e107 before 2.3.5 allows remote attackers to approve or delete comments through a moderator's browser. The comment.php approve and delete handlers execute state changes when session_handler::check() receives no CSRF token because validation runs only when a token is present. Exploitation requires a logged-in administrator or moderator to open an attacker-controlled page, after which arbitrary site comments can be silently approved or deleted.
The record
- CVE
- CVE-2026-46620
- Published
- May 26, 2026
- Updated
- May 26, 2026
- Vendor
- e107
- Product
- e107
- Classifications
- CWE-352, CWE-285, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2026CVE publishedPublication date reported by the CVE source.
- May 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.3.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Cross-origin comment deletion proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo