Taurus Omar

**Name of the Vulnerable Software and Affected Versions** SEO ALert WordPress plugin versions 1.59 and earlier **Description** The SEO ALert WordPress plugin does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered html capability is disallowed, for example in multisite setup. **Recommendations** For SEO ALert WordPress plugin versions 1.59 and earlier, update to a version that addresses this issue. 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** WP Brutal AI WordPress plugin versions prior to 2.06 **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 2.06, update to version 2.06 or later to resolve the issue. As a temporary workaround, consider restricting the ability of high privilege users to access and modify the plugin's settings until the update is applied.

**Name of the Vulnerable Software and Affected Versions** Login Configurator WordPress plugin versions through 2.1 **Description** The issue is related to a reflected cross-site scripting vulnerability. It occurs because the plugin does not properly escape a URL parameter before outputting it to the page, targeting site administrators. **Recommendations** For versions through 2.1, update to a version that properly escapes URL parameters to prevent reflected cross-site scripting. As a temporary workaround, consider restricting access to the plugin's functionality to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** PrePost SEO WordPress plugin versions through 3.0 **Description** The issue arises from the plugin's failure to properly sanitize some of its settings. This could allow high-privilege users to perform Stored Cross-Site Scripting (XSS) attacks, even in scenarios where the unfiltered html capability is disallowed, such as in multisite setups. **Recommendations** For versions through 3.0, consider updating to a version that properly sanitizes settings to prevent Stored Cross-Site Scripting (XSS) attacks. As a temporary workaround, restrict the use of the plugin's settings 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** wpbrutalai WordPress plugin versions prior to 2.0.1 **Description** The issue is related to a Reflected Cross-Site Scripting problem. It occurs because a `parameter` is not properly sanitised and escaped before being outputted back in the page. This could be exploited against high-privilege users, such as admins, who are logged in. **Recommendations** For versions prior to 2.0.1, update to version 2.0.1 or later to resolve the issue. As a temporary workaround, consider restricting access to the plugin's functionality to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** wpbrutalai WordPress plugin versions prior to 2.0.0 **Description** The issue is related to a SQL injection that can be exploited by an admin via CSRF. This occurs because a parameter is not properly sanitized and escaped before being used in a SQL statement. **Recommendations** For versions prior to 2.0.0, update to version 2.0.0 or later to resolve the issue. As a temporary workaround, consider restricting access to the plugin's functionality to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** SEO by 10Web WordPress plugin versions prior to 1.2.7 **Description** The issue is related to the SEO by 10Web WordPress plugin, which does not properly sanitise and escape some of its settings. 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 1.2.7, update to version 1.2.7 or later to resolve the issue. As a temporary workaround, consider restricting access to the plugin's settings for high-privilege users until the update is applied.

**Name of the Vulnerable Software and Affected Versions** Login rebuilder WordPress plugin versions prior to 2.8.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 2.8.1, update to version 2.8.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.

**Name of the Vulnerable Software and Affected Versions** Tablesome WordPress plugin versions prior to 1.0.9 **Description** The issue is related to the Tablesome WordPress plugin, which does not properly escape generated URLs before outputting them in attributes when certain notices are displayed. This leads to Reflected Cross-Site Scripting, allowing a remote attacker to conduct inter-site script attacks. **Recommendations** For versions prior to 1.0.9, update to version 1.0.9 or later to resolve the issue. As a temporary workaround, consider disabling the display of notices that contain generated URLs until a patch is available. Restrict access to the plugin's functionality to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Header Footer Code Manager WordPress plugin versions prior to 1.1.24 **Description** The issue is related to a Reflected Cross-Site Scripting problem. It occurs because the plugin does not properly escape generated URLs before outputting them back in attributes on an admin page. **Recommendations** For versions prior to 1.1.24, update to version 1.1.24 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** WooCommerce WordPress plugin versions prior to 6.6.0 **Description** The issue is related to stored HTML injection due to a lack of escaping and sanitizing in the payment gateway titles. This allows for potential malicious code injection. **Recommendations** For versions prior to 6.6.0, update to version 6.6.0 or later to resolve the issue. As a temporary workaround, consider disabling the payment gateway titles feature until a patch is available. Restrict access to the payment gateway configuration to minimize the risk of exploitation. Avoid using the payment gateway titles in the affected plugin until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** WP Statistics WordPress plugin versions prior to 13.2.2 **Description** The issue arises from the WP Statistics WordPress plugin not sanitizing the `REQUEST URI` parameter before outputting it back in the rendered page. This leads to Cross-Site Scripting (XSS) in web browsers that do not encode characters. **Recommendations** For versions prior to 13.2.2, update to version 13.2.2 or later to resolve the issue. As a temporary workaround, consider restricting access to the plugin's functionality that outputs the `REQUEST URI` parameter until a patch is applied.

**Name of the Vulnerable Software and Affected Versions** Smush WordPress plugin versions prior to 3.9.9 **Description** The issue arises from the Smush WordPress plugin not sanitizing and escaping a configuration parameter before outputting it back in an admin page when uploading a malicious preset configuration, leading to a Reflected Cross-Site Scripting. For the attack to be successful, an attacker would need an admin to upload a malicious configuration file. **Recommendations** For versions prior to 3.9.9, update to version 3.9.9 or later to resolve the issue. As a temporary workaround, consider restricting access to the admin page where the configuration parameter is output to minimize the risk of exploitation. Avoid uploading untrusted configuration files to prevent potential attacks.

**Name of the Vulnerable Software and Affected Versions** LayerSlider WordPress plugin versions prior to 7.1.2 **Description** The issue allows high privilege users, such as admins, to perform Cross-Site Scripting attacks. This is possible because the plugin does not properly sanitise and escape the Project's slug before outputting it in various places, even when the unfiltered html capability is disallowed. **Recommendations** For versions prior to 7.1.2, update to version 7.1.2 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** Anti-Malware Security and Brute-Force Firewall WordPress plugin versions prior to 4.20.96 **Description** The issue arises from the failure to sanitise and escape the QUERY STRING before outputting it back in an admin page, leading to a Reflected Cross-Site Scripting in browsers which do not encode characters. **Recommendations** For versions prior to 4.20.96, update to version 4.20.96 or later to resolve the issue. As a temporary workaround, consider restricting access to admin pages to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Loco Translate WordPress plugin versions prior to 2.6.1 **Description** The issue allows any user with access to the plugin, such as Translator and Administrator, to add arbitrary javascript payloads to the source strings, leading to a stored cross-site scripting (XSS) vulnerability. This occurs because the plugin does not properly remove inline events from elements in the source translation strings before outputting them in the editor in the plugin admin panel. **Recommendations** For versions prior to 2.6.1, update to version 2.6.1 or later to resolve the issue. As a temporary workaround, consider restricting access to the plugin admin panel to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** WP Downgrade versions prior to 1.2.3 **Description** The issue allows high privilege users, such as admins, to perform Cross-Site attacks. This is possible because the plugin only performs client-side validation of its "WordPress Target Version" settings and does not sanitize and escape it server-side, even when the unfiltered html capability is disallowed. **Recommendations** For versions prior to 1.2.3, update to version 1.2.3 or later to resolve the issue. As a temporary workaround, consider restricting access to the plugin's settings to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Hummingbird WordPress plugin versions prior to 3.3.2 **Description** The issue allows high privilege users, such as admins, to perform cross-Site Scripting attacks even when the unfiltered html capability is disallowed, due to the lack of sanitization and escaping of the Config Name. **Recommendations** For versions prior to 3.3.2, update to version 3.3.2 or later to resolve the issue. As a temporary workaround, consider restricting the ability of high privilege users to access the Config Name field until the update is applied.

**Name of the Vulnerable Software and Affected Versions** Ad Inserter Free and Pro WordPress plugins versions prior to 2.7.12 **Description** The issue is related to a Reflected Cross-Site Scripting problem. It occurs because the REQUEST URI is not properly sanitised and escaped before being outputted back in an admin page. This can be particularly problematic in browsers that do not encode characters. **Recommendations** For Ad Inserter Free and Pro WordPress plugins versions prior to 2.7.12, update to version 2.7.12 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** UpdraftPlus WordPress Backup Plugin versions prior to 1.22.9 **Description** The issue is related to a Reflected Cross-Site Scripting (XSS) vulnerability. It occurs because the `updraft interval` parameter is not properly sanitized and escaped before being outputted back in an admin page. **Recommendations** For versions prior to 1.22.9, update to version 1.22.9 or later to resolve the issue. As a temporary workaround, consider restricting access to the admin page that outputs the `updraft interval` parameter to minimize the risk of exploitation.