Threat Intelligence Database

e107 CMS versions 2.3.5 and earlier have a command injection vulnerability in the ImageMagick resize destination path. The vulnerability arises because the destination filename includes user-controlled input that is not properly neutralized, allowing shell command injection under specific configuration settings. Exploitation requires multiple non-default settings to be enabled and a non-admin attacker with certain permissions. This issue is fixed in version 2.3.6.

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.

e107 is a content management system (CMS). Prior to 2.3.4, you can access the local environment by specifying the URL of the local environment from "Image/File URL:" of "From a remote location" in "Media Manager" on the administrator screen. This vulnerability is fixed in 2.3.4.

e107 is a content management system (CMS). Prior to 2.3.4, a Host Header Injection vulnerability in the password reset page allows attackers to manipulate the Host header to generate password reset links pointing to attacker-controlled domains. This can lead to phishing attacks, account takeover, or other security risks. The severity is high, as the vulnerability affects a critical function related to user authentication. This vulnerability is fixed in 2.3.4.

e107 is a content management system (CMS). Prior to 2.3.4, a Broken Access Control vulnerability exists in the application, allowing an unauthorized authenticated user to edit comments posted by others. This stems from inadequate server-side access control validation, where the application depends only on a predictable identifier in the request to determine which comment to edit, without confirming the requesting user’s ownership of the comment. This vulnerability is fixed in 2.3.4.