Bushiyue

**Name of the Vulnerable Software and Affected Versions** Leadster plugin versions prior to 1.1.3 **Description** The issue is related to a Cross-Site Request Forgery (CSRF) vulnerability. This type of vulnerability allows an attacker to trick a user into performing unintended actions on a web application that the user is authenticated to. **Recommendations** For Leadster plugin versions prior to 1.1.3, update to version 1.1.3 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** Patreon WordPress versions 1.8.6 and earlier **Description** The issue is a Cross-Site Request Forgery (CSRF) vulnerability. This type of vulnerability allows an attacker to trick a user into performing unintended actions on a web application that the user is authenticated to. **Recommendations** For versions 1.8.6 and earlier, update to a version later than 1.8.6 to resolve the issue. As a temporary workaround, consider implementing additional CSRF protection measures, such as token-based validation, to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Jonk @ Follow me Darling Sp*tify Play Button for WordPress plugin versions <= 2.10 **Description** The issue is related to a Cross-Site Request Forgery (CSRF) vulnerability. This type of vulnerability allows an attacker to trick a user into performing unintended actions on a web application that the user is authenticated to. **Recommendations** For versions <= 2.10, update to a version that contains a fix for this issue, as using an affected version poses a significant risk. 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** Checkfront Online Booking System plugin versions <= 3.6 **Description** The issue is a Cross-Site Request Forgery (CSRF) vulnerability. This means an attacker can trick a user into performing unintended actions on a web application that the user is authenticated to. No information is provided about the estimated number of potentially affected devices or real-world incidents where this issue was exploited. **Recommendations** For versions <= 3.6, update to a version higher than 3.6 to resolve the issue. At the moment, there is no information about other mitigation measures.