Dariusz Goåda

**Name of the Vulnerable Software and Affected Versions** DirectAdmin Evolution Skin versions prior to 1.668 **Description** The ticket management system in DirectAdmin Evolution Skin is vulnerable to Cross-site Scripting (XSS), which allows a low-privileged user to inject and store malicious JavaScript code. If an admin views the ticket, the script might perform actions with their privileges, including command execution. **Recommendations** For versions prior to 1.668, upgrade to version 1.668 to fix the issue. As a temporary workaround, consider restricting access to the ticket management system to minimize the risk of exploitation. Avoid using the ticket management system until the issue is resolved by upgrading to the fixed version.

**Name of the Vulnerable Software and Affected Versions** HyperView Geoportal Toolkit versions prior to 8.5.0 **Description** The issue allows an unauthenticated remote attacker to prepare links that, when opened, will load scripts from a remote location controlled by the attacker and execute them in the user space. By manipulating a `GET` request parameter, it is also possible to enumerate some of the devices in the Local Area Network in which the server resides. **Recommendations** For versions prior to 8.5.0, update to a patched version as soon as possible and review access controls to mitigate the risk of unauthorized access. As a temporary workaround, consider restricting access to the vulnerable `GET` request parameter until a patch is available.

**Name of the Vulnerable Software and Affected Versions** HyperView Geoportal Toolkit versions prior to 8.2.4 **Description** The issue concerns a Reflected Cross-Site Scripting (XSS) vulnerability. An unauthenticated attacker could trick someone into using a crafted URL, which will cause a script to be run in the user's browser. **Recommendations** For versions prior to 8.2.4, update to version 8.2.4 or later to resolve the issue. As a temporary workaround, consider restricting access to potentially vulnerable URLs to minimize the risk of exploitation. Avoid using crafted URLs that could trigger the execution of malicious scripts in the user's browser.

**Name of the Vulnerable Software and Affected Versions** CemiPark software versions 4.5, 4.7, 5.03 **Description** The access control in CemiPark software does not properly validate user-entered data, allowing for authentication bypass. An attacker with network access to the login panel can log in with administrator rights to the application. **Recommendations** For versions 4.5, 4.7, 5.03, consider restricting access to the login panel to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** CemiPark software versions 4.5, 4.7, 5.03 **Description** The access control in CemiPark software does not properly validate user-entered data, allowing a stored cross-site scripting (XSS) attack. The parameters used to enter data into the system lack appropriate validation, making it possible to smuggle in HTML/JavaScript code, which will be executed in the user's browser space. **Recommendations** For version 4.5, update the input validation mechanism to properly check user-entered data. For version 4.7, implement robust validation for all parameters to prevent XSS attacks. For version 5.03, ensure that all user input is sanitized and validated to prevent code injection. As a temporary workaround, consider restricting user input to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** CemiPark software versions 4.5 through 5.03 **Description** The access control in CemiPark software stores integration credentials, such as FTP or SIP, in plain-text. An attacker who gains unauthorized access to the device can retrieve clear text passwords used by the system. **Recommendations** For versions 4.5 through 5.03, consider restricting access to the device to minimize the risk of exploitation. As a temporary workaround, avoid using plain-text credentials for integrations until a fix is available. At the moment, there is no information about a newer version that contains a fix for this vulnerability.