Arpeet Rathi

**Name of the Vulnerable Software and Affected Versions** The Events Calendar BookIt versions 2.4.0 and earlier **Description** The issue is related to improper validation of specified quantity in input, allowing manipulation of hidden fields. This can be exploited to potentially alter or access unauthorized data. **Recommendations** For versions 2.4.0 and earlier, update to a version later than 2.4.0 to resolve the 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** Meks Smart Social Widget plugin for WordPress versions up to, and including, 1.6.3 **Description** The issue is related to Stored Cross-Site Scripting via the Meks Smart Social Widget, caused by insufficient input sanitization and output escaping. This allows authenticated attackers with administrator-level access to inject arbitrary web scripts in pages, which will execute when a user accesses an injected page. The issue only affects multi-site installations and installations where unfiltered html has been disabled. **Recommendations** For Meks Smart Social Widget plugin for WordPress versions up to, and including, 1.6.3, update to a version later than 1.6.3 to resolve the issue. As a temporary workaround, consider restricting access to the Meks Smart Social Widget to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** FooGallery plugin for WordPress versions up to, and including, 2.3.3 **Description** The FooGallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the custom attributes due to insufficient input sanitization and output escaping. This allows contributors and above to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. **Recommendations** For FooGallery plugin for WordPress versions up to, and including, 2.3.3, update to a version later than 2.3.3 to resolve the issue. As a temporary workaround, consider restricting access to the custom attributes feature to minimize the risk of exploitation.