The Monstra CMS 3.0.4 allows remote attackers to execute arbitrary code via crafted PHP code in a .chunk.php file.
Prints get request between script tags on page
Monstra CMS 3.0.4 allows remote attackers to delete folder via an admin/index.php?id=filesmanager&delete_dir=./&path=uploads/ request.
Monstra CMS 3.0.4 has a stored XSS vulnerability when an attacker has access to the editor role, and enters the payload in the content section of a new page in the blog catalog.
Monstra CMS is prone to an SQL-injection vulnerability because it fails to sufficiently sanitize user-supplied data before using it in an SQL query. Exploiting this issue could allow an attacker to compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database.
MonstraCMS 3.0.4 allows users to upload arbitrary files which leads to a remote command execution on the remote server. An attacker can upload a file with a PHP extension containing malicious code and execute system commands by adding ?cmd= to the URL.
Any user can change credentials of other users including the Administrator credentials. This can allow the attacker to gain Administrator access and completely compromise the application. Once logged in as a regular user or successfully registering as a new user, use the following URL to gain information (username) of other users: http://localhost/monstra-3.0.3/users/1. The digit '1' is of Admin or first user created in the database. By changing the digit, all registered usernames can be found. Then by using the 'Edit Profile' option of own user account, password of any other user including the Administrator can be changed by changing the POST parameters 'user_id', 'login' and 'new_password'.
Monstra CMS through 3.0.4 has an incomplete "forbidden types" list that excludes .php (and similar) file extensions but not the .pht or .phar extension, which allows remote authenticated Admins or Editors to execute arbitrary PHP code by uploading a file, a different vulnerability than CVE-2017-18048.
Monstra CMS version 3.0.4 and earlier is vulnerable to Cross-Site Scripting. An attacker can exploit this vulnerability by intercepting the first request through a proxy tool to verify the CSRF token and then sending a malicious script to the target. This can be done by sending a POST request to the target with the malicious script in the 'page_title' parameter.