Shreya Pohekar

The issue concerns a lack of CSRF check in some areas and missing sanitization as well as escaping in the User registration & user profile WordPress plugin. This could allow attackers to make logged-in admins add Stored XSS payloads via a CSRF attack.

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.

The issue concerns a lack of CSRF check when creating and editing shortcodes in the plugin, along with missing sanitization and escaping. This could allow attackers to make logged-in admins add Stored XSS payloads via a CSRF attack.

The issue concerns a lack of validation for URLs input in the admin panel or in shortcodes for showing events from a remote .ics file. This allows an attacker with privileges as low as Subscriber to perform Server-Side Request Forgery (SSRF) attacks on the site's internal network.

The issue arises from the plugin's failure to properly escape POST values, which are then printed back to the user inside one of the plugin's administrative pages. This allows for reflected XSS attacks targeting administrators. The vulnerability can be exploited by a remote attacker to conduct a cross-site scripting (XSS) attack.

The issue allows high-privilege users to perform Stored Cross-Site Scripting (XSS) attacks due to improper sanitization of some settings, even when the unfiltered html capability is disallowed, such as in multisite setups.

The issue is related to a Reflected Cross-Site Scripting problem. It occurs because a parameter is not properly sanitized and escaped before being outputted back in the page. This could be exploited against high-privilege users, such as administrators.

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 multisite setups. This is due to the plugin not sanitizing and escaping some of its settings.

The issue is related to Reflected Cross-Site Scripting, which occurs because the plugin does not properly sanitise and escape various parameters before outputting them back in pages. This could be used against high privilege users such as admin.

The issue is related to a Stored Cross-Site Scripting vulnerability. It occurs because the `url` parameter in the "rapidexpcart" endpoint is not properly sanitized and escaped before being stored and outputted back in the page. This could be exploited against high-privilege users, such as admins. Additionally, the lack of CSRF protection allows an attacker to trick a logged-in admin into performing the attack by submitting a hidden form.

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 multisite setups. This is due to the plugin not sanitizing and escaping some of its settings.

The issue allows unauthenticated attackers to trick a logged-in admin into triggering a XSS payload by clicking a link, due to the lack of sanitization and escaping of the query parameter `ricerca` before outputting it in an admin panel.

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 administrators.

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 multisite setups. This is due to the plugin not sanitizing and escaping some of its settings.

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.

The issue concerns the amr ical events lists 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.

The issue is related to the lack of CSRF protection and insufficient sanitizing and escaping of parameters, allowing attackers to make a logged-in admin put Stored Cross-Site Scripting payloads via CSRF. This enables attackers to potentially execute malicious scripts on the site.

The issue arises from improper sanitization of the `publish terms text` setting, which can be exploited to conduct Stored XSS attacks, particularly in multisite environments. This could potentially allow administrators to execute malicious scripts.

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 administrators.

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 multisite setups. This is due to the plugin not sanitizing and escaping some of its settings.