/

CVE-2026-19899

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in Class Exam Timetabling System

CVE-2026-19899

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Unauthorized Database Access and Data Manipulation

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A high-severity SQL injection vulnerability in the Class and Exam Timetabling System 1.0 may allow a remote attacker to influence database queries through the ID argument handled by /edit_teacher.php.

When that input is incorporated into a database operation without adequate parameterization or validation, an attacker could access, alter, or otherwise affect application data.

Affected context

The vulnerability occurs in deployments of SourceCodester Class and Exam Timetabling System 1.0 where the /edit_teacher.php endpoint is remotely reachable and processes the ID parameter in a database query. Risk is greater when the endpoint lacks effective authorization controls, input validation, or database-account restrictions.

Exploit preconditions

  • Attack surface: The remotely accessible /edit_teacher.php web endpoint
  • Required access: Network access to the application; authentication requirements depend on the deployment
  • Trigger point: Processing of the ID argument during teacher-record editing
  • Why exploitation is possible: User-controlled input may influence SQL query construction without sufficient separation between data and query instructions

Why this happens

The underlying issue is improper neutralization of special elements in SQL commands, mapping primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'). The related CWE-74 classification reflects the broader injection pattern, in which externally supplied data is interpreted as part of an instruction rather than treated strictly as a value. This commonly results from dynamically assembling SQL statements with untrusted request parameters.

Potential impact

  • An attacker may read unauthorized database records
  • An attacker could modify or delete application data
  • Sensitive user, teacher, or scheduling information may be exposed
  • Database availability could be affected
  • The application may be used as a foothold for broader compromise, depending on database privileges and deployment controls

General mitigation guidance

Mitigation generally focuses on ensuring that request data cannot alter SQL statement structure.

Common defensive patterns include:

  • Use parameterized queries or prepared statements for all database operations
  • Apply allowlist validation and type constraints to identifier parameters
  • Enforce authorization checks before editing teacher records
  • Use a database account with only the privileges required by the application
  • Avoid exposing detailed database errors to remote users
  • Treat all client-supplied parameters as untrusted, including values that appear numeric

How teams detect issues like this

Detection approaches commonly include:

  • Static analysis for string concatenation or interpolation of request parameters into SQL statements
  • Code review of database calls reachable from /edit_teacher.php
  • Dynamic application testing for unexpected query behavior using controlled, non-destructive test cases
  • Web-application firewall or database monitoring rules for anomalous request and query patterns
  • Policy checks requiring prepared statements and rejecting direct construction of SQL commands from user input
  • Review of database audit logs for unusual access, modification, or error patterns

Sources

SourceLink
github.comgithub.com/endingstory/e/issues/1
vuldb.comvuldb.com/cve/CVE-2026-19899
vuldb.comvuldb.com/submit/870682
vuldb.comvuldb.com/vuln/390089
vuldb.comvuldb.com/vuln/390089/cti
sourcecodester.comsourcecodester.com/

Frequently asked

questions

Yes. The reported attack surface is a remotely accessible web endpoint, although actual exploitability depends on network exposure, authentication, and authorization controls.

Not necessarily. The required access depends on how the application protects /edit_teacher.php; any account or network access that reaches the vulnerable operation may be relevant.

Use parameterized database queries, validate identifier inputs against an expected format, and enforce authorization before performing the requested record operation.

Establish secure database-access standards, review all request-to-query data flows, apply least-privilege database permissions, and include SQL injection testing in code review and automated security testing.

Find out what's already
exploitable in your codebase.