e107: CSRF in comment.php moderation endpoints via token-optional validation in session_handler::check()
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| e107inc | e107 | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| E107 | E107 |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.133% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
E107
E107 e107 |
|
| Vendors & Products |
E107
E107 e107 |
| Type | Values Removed | Values 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. | |
| Title | e107: CSRF in comment.php moderation endpoints via token-optional validation in session_handler::check() | |
| Weaknesses | CWE-285 CWE-352 |
|
| References |
| |
| Metrics |
cvssV3_1
|