A critical SQL injection vulnerability in the code-projects Student Web Portal allows unauthenticated remote attackers to compromise database integrity.

This flaw is a SQL injection vulnerability (CWE-89) located in the check_user.php script, specifically affecting the Username parameter. The vulnerability allows an unauthenticated remote attacker to inject malicious SQL commands, potentially leading to unauthorized data access or manipulation.

Successful exploitation of this vulnerability poses a significant risk to the confidentiality and integrity of student data stored within the portal. Given the CVSS score of 7.3, this high-severity flaw could lead to unauthorized database access, potentially facilitating further lateral movement or data exfiltration. The ability for an unauthenticated attacker to interact with the back-end database makes this an urgent security concern for organizations hosting this software.

Immediate Action: As no official patch is currently available, administrators should restrict network access to the Student Web Portal and specifically block requests targeting the check_user.php file until a vendor-supplied update is released.

Proactive Monitoring: Security teams should review server access logs for anomalous HTTP requests containing SQL syntax, particularly those directed at check_user.php, and monitor database logs for unexpected query patterns.

Compensating Controls: Implement a Web Application Firewall (WAF) rule to detect and block common SQL injection patterns targeting the Username parameter, which can serve as a effective virtual patch while awaiting a formal fix.

Public Exploit Available: Yes, a public proof-of-concept exists, attributed to the research documentation provided via the VulDB and GitHub references.

The presence of a public proof-of-concept for this SQL injection vulnerability significantly lowers the barrier for exploitation by malicious actors. Organizations currently utilizing code-projects Student Web Portal 1.0 must immediately implement WAF-based mitigations and restrict access to the affected endpoint to prevent potential data compromise. Prioritize migration to a more secure platform if the vendor does not provide a timely security update.