Description

A weakness has been identified in SourceCodester Class and Exam Timetabling System 1.0. This vulnerability affects unknown code of the file /edit_subject2.php. Executing a manipulation of the argument ID can lead to sql injection. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "7.3",
  "pubDate": "2026-08-18T00:16:53.380Z",
  "pubdate": "2026-08-18T00:16:53.380Z",
  "executiveSummary": "An identified security vulnerability exists within the SourceCodester Class and Exam Timetabling System 1.0, specifically within the /edit_subject2.php endpoint. The flaw manifests as an SQL injection vulnerability arising from the improper sanitization and neutralization of user-supplied input passed through the ID argument. An unauthenticated or remote attacker can exploit this weakness by manipulating the ID parameter to inject malicious SQL syntax directly into database queries executed by the backend application.\nThe impact of successful exploitation includes unauthorized access to the underlying database, potential extraction of sensitive information, data tampering, or complete compromise of the database management system depending on database user privileges. Because public exploits for this vulnerability are currently available, the risk to vulnerable deployments is critical. Immediate remediation is required to protect affected systems from remote exploitation.",
  "technicalDetails": "The root cause of the vulnerability resides in the insecure handling of dynamic input parameters within the /edit_subject2.php file of the SourceCodester Class and Exam Timetabling System 1.0. Specifically, the application accepts user-supplied data via the ID argument without implementing adequate input validation, type casting, or parameterized query structures (such as prepared statements). Consequently, the input is concatenated directly into SQL query strings executed by the database engine.\nThe attack flow begins when an attacker crafts a malicious HTTP request targeting the /edit_subject2.php script. By supplying specially crafted SQL payloads within the ID parameter, the attacker alters the intended logical structure of the database query. Because the application processes the untrusted input directly, the database interprets the injected strings as executable SQL commands rather than literal parameter values.\nExploitation is feasible over the network, allowing remote threat actors to execute the attack without prior authentication or special privilege requirements, assuming public network exposure of the web application. Depending on the construction of the vulnerable query and database configurations, the attack vector may facilitate techniques such as union-based SQL injection, error-based extraction, or boolean-blind inference.\nThe post-exploitation impact includes unauthorized retrieval of confidential records stored within the database, modification or deletion of application data, and potential execution of administrative database operations. Remediation requires refactoring the vulnerable component to utilize parameterized queries or prepared statements for all database interactions involving user-supplied parameters."
}