A critical SQL injection vulnerability in code-projects Scholars Tracking System 1.0 permits unauthenticated remote attackers to compromise database integrity and confidentiality.

The application fails to sanitize the id parameter in the /admin/delete_user.php script before incorporating it into database queries. This vulnerability allows an unauthenticated attacker to inject malicious SQL commands, enabling unauthorized data access or manipulation.

Successful exploitation allows an attacker to bypass authentication, extract sensitive information, modify or delete database records, and potentially gain full control over the underlying database. While the CVSS score of 7.3 reflects the high impact on data confidentiality and integrity, the ability for an unauthenticated attacker to perform these actions poses an immediate threat to business continuity and data privacy.

Immediate Action: As no official patch is currently available, administrators should restrict network access to the /admin/ directory and implement strict input validation on all parameters. If the system is not critical, consider taking the application offline until the vendor provides a secure update.

Proactive Monitoring: Monitor web server logs for suspicious URL parameters containing SQL syntax, such as "SLEEP", "UNION", or comment characters like "#" or "--". Review database query logs for anomalous execution patterns originating from the /admin/delete_user.php endpoint.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block common SQL injection patterns targeting the identified vulnerable parameter. Ensure that the database user account used by the web application is restricted to the minimum necessary privileges to limit the scope of potential damage.

Public Exploit Available: Yes, a published proof-of-concept exists, as documented in the GitHub issue referenced by the researcher.

Given the availability of a public proof-of-concept and the ease of exploitation, this vulnerability represents a significant risk to any organization hosting the Scholars Tracking System. Organizations must prioritize restricting access to the affected script immediately and remain vigilant for vendor updates, as the lack of an official patch makes proactive defensive measures and network-level filtering essential for protection.