Liu_My

**Name of the Vulnerable Software and Affected Versions** Codezips Gym Management System version 1.0 **Description** A critical issue affects the processing of the file /dashboard/admin/health status entry.php, where the manipulation of the `usrid` argument leads to SQL injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. **Recommendations** For Codezips Gym Management System version 1.0, as a temporary workaround, consider restricting access to the /dashboard/admin/health status entry.php file until a patch is available. Avoid using the `usrid` argument in the affected file 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** code-projects Fantasy-Cricket version 1.0 **Description** A critical issue has been found, allowing for SQL injection through the manipulation of the `uname` argument in an unknown function of the file /dash/update.php. This can be exploited remotely. The issue has been publicly disclosed and may be used for attacks. **Recommendations** For code-projects Fantasy-Cricket version 1.0, as a temporary workaround, consider restricting access to the /dash/update.php file until a patch is available. Avoid using the `uname` 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 issue.

**Name of the Vulnerable Software and Affected Versions** code-projects Fantasy-Cricket version 1.0 **Description** A critical issue has been found in the code-projects Fantasy-Cricket software. The vulnerability is a remote SQL injection in the /authenticate.php file, which can be exploited by manipulating the `uname` argument. This can be launched remotely and an exploit has been publicly disclosed. **Recommendations** For version 1.0, consider disabling the `uname` argument in the /authenticate.php file as a temporary workaround until a patch is available. Restrict access to the /authenticate.php file to minimize the risk of exploitation. Avoid using the `uname` argument in the affected API endpoint until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this vulnerability.