CVE-2025-14621
7.3code-projects · Student File Management System
A SQL injection vulnerability in the Student File Management System 1.0 allows remote, unauthenticated attackers to manipulate the user_id argument in /admin/update_user.php.
Executive summary
A critical SQL injection vulnerability in the code-projects Student File Management System 1.0 exposes the application to remote, unauthenticated data manipulation.
Vulnerability
The application is susceptible to SQL injection via the user_id parameter within the /admin/update_user.php script. This flaw permits an unauthenticated remote attacker to inject malicious SQL commands, potentially compromising the integrity of the backend database.
Business impact
The vulnerability carries a CVSS score of 7.3, indicating a high risk to organizational data integrity. Successful exploitation could allow an attacker to bypass authentication, extract sensitive information, or modify database records, leading to potential service disruption and unauthorized access to student records.
Remediation
Immediate Action: Since no official patch is currently available, administrators should restrict network access to the /admin/update_user.php endpoint or disable the affected module until a vendor update is released.
Proactive Monitoring: Review web server access logs for anomalous requests containing SQL syntax patterns or unexpected character strings targeting the user_id parameter.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules specifically configured to detect and block SQL injection attempts against the identified vulnerable endpoint.
Exploitation status
Public Exploit Available: Yes, a public proof-of-concept exists, as documented in the linked GitHub repository.
Analyst recommendation
Given the availability of a public proof-of-concept and the lack of a vendor patch, this vulnerability poses a significant risk to affected systems. Organizations should prioritize isolating the vulnerable component from public-facing networks and implement strict input validation via WAF filtering to prevent unauthorized database access.
More code-projects CVEs
Sources
Originally found and disclosed by jjjjjzr (VulDB User), per the CVE Program record.