Ceylan Bozogullarindan

**Name of the Vulnerable Software and Affected Versions** CM News versions through 6.0 **Description** The issue affects CM News, allowing SQL Injection due to improper neutralization of special elements used in an SQL command. This enables attackers to execute malicious SQL commands. The vendor was contacted, and it was learned that the product is not supported. **Recommendations** For CM News versions through 6.0, as a temporary workaround, consider restricting access to the SQL command functionality until a patch is available, but since the product is not supported, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** iQ Block Country WordPress plugin versions prior to 1.2.13 **Description** The issue allows an authorized user to import preconfigured settings of the plugin by uploading a zip file. During the extraction process of the uploaded zip file, files are extracted one by one and their existence is checked. If a file exists, it is deleted without any security control, considering only the name of the extracted file. This behavior leads to a "Zip Slip" vulnerability. **Recommendations** For versions prior to 1.2.13, update to version 1.2.13 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** Error Log Viewer WordPress plugin versions prior to 1.1.2 **Description** The issue allows high privilege users to clear arbitrary files on the web server, including those outside of the blog folder, due to a lack of validation of the log file path to clear. **Recommendations** For Error Log Viewer WordPress plugin versions prior to 1.1.2, update to version 1.1.2 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** StatCounter WordPress plugin versions prior to 2.0.7 **Description** The issue allows high privilege users to perform Cross-Site Scripting attacks due to the lack of sanitization and escaping of the `Project ID` and `Secure Code` settings, even when the `unfiltered html` capability is disallowed. **Recommendations** For versions prior to 2.0.7, update to version 2.0.7 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** LearnPress WordPress plugin versions prior to 4.1.5 **Description** The issue allows users to upload an image as a profile avatar after registration, which is then cropped and saved. A "POST" request is sent to the server to rename and crop the image, changing the user-supplied image name to an MD5 value. This process is limited to JPG or PNG image types. An attacker can exploit this to rename an arbitrary image file, potentially disrupting the website's design. **Recommendations** For versions prior to 4.1.5, update to version 4.1.5 or later to resolve the issue. As a temporary workaround, consider restricting the image upload functionality to trusted users or disabling the image cropping and renaming feature until the update is applied.

**Name of the Vulnerable Software and Affected Versions** Mortgage Calculators WP WordPress plugin versions prior to 1.56 **Description** The issue concerns a lack of sanitization on the color setting of the background of a calculator. This could allow high privilege users to perform Stored Cross-Site Scripting attacks, even when the unfiltered html capability is disallowed. **Recommendations** For Mortgage Calculators WP WordPress plugin versions prior to 1.56, update to version 1.56 or later to resolve the issue. As a temporary workaround, consider restricting access to the calculator settings to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Domain Check WordPress plugin versions prior to 1.0.17 **Description** The issue is related to a Reflected Cross-Site Scripting problem. It occurs because the `domain` parameter is not properly sanitised and escaped before being outputted back in the page. This allows for malicious scripts to be injected and executed. **Recommendations** For versions prior to 1.0.17, update to version 1.0.17 or later to resolve the issue. As a temporary workaround, consider restricting access to the `domain` parameter to minimize the risk of exploitation.