CVE-2026-86268

7.3

itsourcecode · School Management System

The School Management System 1.0 is vulnerable to SQL injection via the email parameter in User_Login.php, allowing unauthenticated remote attackers to execute arbitrary database queries.

Executive summary

The School Management System 1.0 contains a critical SQL injection vulnerability that allows unauthenticated remote attackers to compromise backend database operations.

Vulnerability

This vulnerability is a classic SQL injection flaw located in the User_Login.php file. The application fails to sanitize the email parameter, which is processed via POST requests, allowing an unauthenticated attacker to inject malicious SQL commands directly into the database query.

Business impact

Successful exploitation of this vulnerability can lead to unauthorized access to sensitive application data, potential modification of user credentials, or unauthorized administrative actions. Given the CVSS score of 7.3, this flaw poses a significant risk to the confidentiality and integrity of the system, potentially facilitating full application compromise.

Remediation

Immediate Action: Since no official patch is currently available, administrators should restrict access to the application or implement strict input validation on the email parameter to block malicious characters. If possible, disable the vulnerable login endpoint until a vendor-supplied update is released.

Proactive Monitoring: Monitor server access logs for suspicious POST requests to User_Login.php, specifically looking for unusual character patterns or SQL syntax in the email field.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block common SQL injection payloads targeted at the login interface.

Exploitation status

Public Exploit Available: Yes, a published proof-of-concept exists, as documented in the referenced security research write-up on GitHub.

Analyst recommendation

The presence of a public proof-of-concept necessitates immediate defensive action. Organizations utilizing this software must prioritize restricting external access to the vulnerable endpoint and implementing robust WAF filtering to mitigate the risk of exploitation while awaiting a formal security update from the vendor.

More itsourcecode CVEs all →

Sources

Originally found and disclosed by anglemsg (VulDB User), per the CVE Program record.