Hexifeo

The issue arises from an incomplete '.htaccess' file for blacklist filtering on the product page, which fails to prevent the execution of files with the '.pht' extension. This allows remote authenticated administrators to upload '.pht' files, leading to arbitrary PHP code execution. The exploitation occurs via the "/catalog/admin/categories.php?cPath=&action=new product" API endpoint, specifically by manipulating the `cPath` and `action` variables.

The issue is related to an incomplete '.htaccess' file for blacklist filtering in the product page, allowing remote authenticated administrators to upload new '.htaccess' files. This can lead to arbitrary PHP code execution via the "/catalog/admin/categories.php?cPath=&action=new product" API endpoint, specifically by manipulating the `cPath` and `action` variables.

The issue allows remote attackers to execute arbitrary PHP code via a .pht or .phar file. This is because the .htaccess file omits these file types, specifically affecting the `/panel/uploads` endpoint.

The issue allows HTML execution through alternative file uploads. This can occur with files having no extension or unrecognized extensions, such as 'test' or 'test.asdf', due to vulnerabilities in admin/upload-uploadify.php and the validate safe file function in admin/inc/security functions.php.

The issue concerns the upload functionality in GetSimpleCMS, where the `admin/upload.php` blocks uploads of `.html` files, but Internet Explorer can still render HTML elements in a `.eml` file. This is due to the `admin/upload-uploadify.php` and the `validate safe file` function in `admin/inc/security functions.php`.

The issue allows remote authenticated administrators to execute arbitrary code by uploading an executable file.

The issue allows remote authenticated administrators to upload .htaccess files, which could potentially lead to security problems.

The issue is related to an incomplete '.htaccess' file for blacklist filtering in the product page, allowing alternative cases for HTML execution. This includes files with no extension or unrecognized extensions, such as 'test' or 'test.asdf'.

The issue concerns an incomplete '.htaccess' file for blacklist filtering in the product page of osCommerce. Specifically, the .htaccess file in the catalog/images/ directory bans the html extension, but Internet Explorer can render HTML elements in a .eml file.

The issue is related to an incomplete '.htaccess' file for blacklist filtering in the product page. Specifically, the .htaccess file in catalog/images/ bans the html extension, but there are several extensions, such as the svg extension, in which contained HTML can be executed.

The issue concerns stored XSS that can be triggered by remote authenticated administrators. This occurs when a file without an extension is uploaded, and in certain cases, this file is interpreted as text/html, allowing JavaScript content to be executed. The estimated number of potentially affected devices worldwide is not specified. Details about real-world incidents where this issue was exploited are not provided. The API endpoint "/admin/index.php?id=filesmanager" is involved, and the `id` variable is used to access the files manager. The lack of a file extension allows the file to be interpreted as text/html.

The issue is related to an incomplete list of forbidden file types, allowing remote authenticated Admins or Editors to execute arbitrary PHP code by uploading files with certain extensions, such as .pht or .phar.