An unauthenticated SQL injection vulnerability in the School Registration and Fee System 1.0 poses a critical risk of full database compromise and unauthorized data access.

This vulnerability is an SQL injection flaw located in the /bilal/normal/pay_report.php file. It stems from the application failing to properly sanitize user-supplied input in the period parameter, allowing an unauthenticated attacker to inject malicious SQL commands directly into the backend database.

Successful exploitation of this vulnerability allows unauthorized actors to bypass authentication, extract sensitive student and financial data, modify or delete records, and potentially gain full control over the underlying database server. Given the CVSS score of 7.3, this represents a high-severity risk that could lead to significant regulatory non-compliance, severe reputational damage, and operational disruption of educational administrative services.

Immediate Action: As no official vendor patch is currently available, administrators should restrict network access to the affected script or place the application behind a robust Web Application Firewall (WAF) configured to block SQL injection patterns.

Proactive Monitoring: Review database access logs for anomalous query patterns, such as unexpected use of UNION operators, time-based sleep commands, or repetitive error logs originating from the /bilal/normal/pay_report.php endpoint.

Compensating Controls: Implement strict input validation at the application layer and ensure the database service account operates with the principle of least privilege, specifically restricting access to only the tables absolutely required for system operations.

Public Exploit Available: Yes, a published proof-of-concept exists and is attributed to the researcher's technical write-up on GitHub.

Due to the ease of exploitation and the potential for full database compromise, organizations utilizing SourceCodester School Registration and Fee System 1.0 must prioritize the implementation of compensating controls immediately. Given the lack of a vendor-supplied patch, migrating to a more secure alternative or isolating the affected system from the public internet is strongly advised to mitigate the risk of data exfiltration.