Jonatas Souza Villa Flor

**Name of the Vulnerable Software and Affected Versions** Vrm 360 3D Model Viewer WordPress plugin versions 1.2.1 and earlier **Description** The issue arises from insufficient checks in a plugin shortcode, allowing for arbitrary file upload. **Recommendations** For Vrm 360 3D Model Viewer WordPress plugin versions 1.2.1 and earlier, consider disabling the vulnerable shortcode until a patch is available to prevent arbitrary file uploads.

**Name of the Vulnerable Software and Affected Versions** Enable Media Replace WordPress plugin versions prior to 4.1.3 **Description** The issue allows Author+ users to perform PHP Object Injection when a suitable gadget is present on the blog, due to the unserialize of user input via the Remove Background feature. **Recommendations** For versions prior to 4.1.3, update to version 4.1.3 or later to resolve the issue. As a temporary workaround, consider restricting access to the Remove Background feature for Author+ users until the update is applied.

**Name of the Vulnerable Software and Affected Versions** Vrm 360 3D Model Viewer WordPress plugin versions 1.2.1 and earlier **Description** The issue exposes the full path of a file when a non-existent file is specified in a parameter of the shortcode. **Recommendations** For versions 1.2.1 and earlier, consider updating to a version that fixes this issue, as the current version exposes sensitive file path information. 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** Import XML and RSS Feeds WordPress plugin versions prior to 2.1.4 **Description** The issue allows an attacker to upload a malicious PHP file due to a lack of file extension filtering for uploaded files, leading to Remote Code Execution. **Recommendations** For versions prior to 2.1.4, update to version 2.1.4 or later to resolve the issue. As a temporary workaround, consider restricting file uploads to prevent potential exploitation until the update is applied.

**Name of the Vulnerable Software and Affected Versions** Serial Codes Generator and Validator with WooCommerce Support WordPress plugin versions prior to 2.4.15 **Description** The issue concerns the Serial Codes Generator and Validator with WooCommerce Support WordPress plugin, where some settings are not properly sanitized and escaped. This could allow high-privilege users, such as administrators, to perform Stored Cross-Site Scripting attacks, even when the unfiltered html capability is disallowed, for example, in a multisite setup. **Recommendations** For versions prior to 2.4.15, update to version 2.4.15 or later to resolve the issue. As a temporary workaround, consider restricting access to the plugin's settings to minimize the risk of exploitation. Additionally, ensure that the unfiltered html capability is properly configured and restricted to trusted users.

**Name of the Vulnerable Software and Affected Versions** wpDataTables versions prior to 2.1.66 **Description** The issue concerns the deserialization of arbitrary data due to a lack of validation of the `Serialized PHP array` input data. This can potentially lead to remote code execution if a suitable gadget chain is present on the server, particularly impacting environments where admin users should not be allowed to execute arbitrary code, such as multisite. **Recommendations** For versions prior to 2.1.66, update to version 2.1.66 or later to resolve the issue. As a temporary workaround, consider restricting access to the deserialization functionality to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** 123.chat WordPress plugin versions prior to 1.3.1 **Description** The issue allows high privilege users, such as admins, to perform Stored Cross-Site Scripting attacks, even when the unfiltered html capability is disallowed, for example, in a multisite setup. This is due to the plugin not sanitizing and escaping some of its settings. **Recommendations** For versions prior to 1.3.1, update to version 1.3.1 or later to resolve the issue. As a temporary workaround, consider restricting the use of the plugin's settings to minimize the risk of exploitation.