Y4Ng0615

**Name of the Vulnerable Software and Affected Versions** Melapress File Monitor WordPress plugin versions prior to 2.1.0 **Description** The issue allows admins to perform SQL injection attacks due to a parameter not being sanitized and escaped before use in a SQL statement. **Recommendations** For versions prior to 2.1.0, update to version 2.1.0 or later to resolve the issue.

Name of the Vulnerable Software and Affected Versions: Auto Affiliate Links WordPress plugin versions prior to 6.4.7 Description: The issue allows administrators to perform SQL injection attacks due to the lack of sanitization and escaping of a parameter before it is used in a SQL statement. Recommendations: For versions prior to 6.4.7, update to version 6.4.7 or later to resolve the issue.

Name of the Vulnerable Software and Affected Versions: Melapress File Monitor versions prior to 2.1.1 Description: The issue allows admins to perform SQL injection attacks due to a parameter not being sanitized and escaped before use in a SQL statement. Recommendations: For versions prior to 2.1.1, update to version 2.1.1 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** WP-Recall WordPress plugin versions prior to 16.26.12 **Description** The issue allows admins to perform SQL injection attacks due to the lack of sanitization and escaping of a parameter before using it in a SQL statement. **Recommendations** For versions prior to 16.26.12, update to version 16.26.12 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** Recover WooCommerce Cart Abandonment, Newsletter, Email Marketing, Marketing Automation By FunnelKit WordPress plugin versions prior to 3.3.0 **Description** The issue allows unauthenticated users to perform SQL injection attacks due to the lack of sanitization and escaping of the `bwfan-track-id` parameter before using it in a SQL statement. **Recommendations** For versions prior to 3.3.0, update to version 3.3.0 or later to resolve the issue. As a temporary workaround, consider restricting access to the SQL statement that uses the `bwfan-track-id` parameter until a patch is available. Avoid using the `bwfan-track-id` parameter in affected SQL statements until the issue is resolved.