Moye

**Name of the Vulnerable Software and Affected Versions** School Activity Updates with SMS Notification version 1.0 **Description** The issue is related to a SQL injection vulnerability. This vulnerability can be exploited via the `/modules/user/index.php?view=edit&id=` component. The `id` parameter is vulnerable to SQL injection attacks. **Recommendations** For School Activity Updates with SMS Notification version 1.0, consider disabling the `/modules/user/index.php?view=edit&id=` component until a patch is available. Restrict access to this component to minimize the risk of exploitation. Avoid using the `id` parameter 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.

**Name of the Vulnerable Software and Affected Versions** School Activity Updates with SMS Notification version 1.0 **Description** The issue is related to a SQL injection vulnerability. This vulnerability can be exploited via the `/modules/autonumber/index.php?view=edit&id=` component. The `id` parameter is vulnerable to SQL injection attacks. **Recommendations** For School Activity Updates with SMS Notification version 1.0, consider restricting access to the `/modules/autonumber/index.php?view=edit&id=` endpoint until a patch is available. As a temporary workaround, avoid using the `id` parameter 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.

**Name of the Vulnerable Software and Affected Versions** School Activity Updates with SMS Notification version 1.0 **Description** The issue is related to a SQL injection vulnerability. It can be exploited via the `/modules/modstudent/index.php?view=edit&id=` component. **Recommendations** For School Activity Updates with SMS Notification version 1.0, consider restricting access to the `/modules/modstudent/index.php?view=edit&id=` endpoint until a patch is available. As a temporary workaround, avoid using the `id` parameter in the affected endpoint to minimize the risk of exploitation.