Vishnudev1

**Name of the Vulnerable Software and Affected Versions** PHPGurukul Tourism Management System version 1.0 **Description** A problematic vulnerability has been found in the PHPGurukul Tourism Management System. The issue affects an unknown function of the file user-bookings.php, where the manipulation of the `Full Name` argument leads to cross-site scripting. This attack can be launched remotely. The exploit has been disclosed to the public. **Recommendations** For PHPGurukul Tourism Management System version 1.0, consider disabling the `user-bookings.php` file or restricting access to it until a patch is available. As a temporary workaround, avoid using the `Full Name` argument in the affected function 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** CodeAstro Restaurant POS System version 1.0 **Description** A problematic issue has been found in the CodeAstro Restaurant POS System, affecting some unknown functionality of the file create account.php. The manipulation of the `Full Name` argument leads to cross-site scripting. The attack can be launched remotely. **Recommendations** For CodeAstro Restaurant POS System version 1.0, consider disabling the create account.php file or restricting access to it until a patch is available. Avoid using the `Full Name` argument in the affected functionality to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this issue.

**Name of the Vulnerable Software and Affected Versions** CodeAstro Restaurant POS System version 1.0 **Description** A critical issue was found in the CodeAstro Restaurant POS System, affecting an unknown part of the file update product.php. This issue leads to unrestricted upload and can be initiated remotely. The exploit has been disclosed to the public. **Recommendations** For CodeAstro Restaurant POS System version 1.0, consider restricting access to the update product.php file to minimize the risk of exploitation. As a temporary workaround, avoid using the file until a patch is available. At the moment, there is no information about a newer version that contains a fix for this issue.