/

CVE-2026-86208

Severity:

HIGH RISK

(7.3)

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

CVE-2026-86208

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Database Manipulation and Unauthorized Data Access

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 SQL injection vulnerability in the Class and Exam Timetabling System allows attacker-controlled input in the ID argument of /delete_teacher.php to influence database queries. Because the endpoint is remotely accessible, an unauthenticated or otherwise unauthorized attacker may be able to manipulate database operations if access controls do not prevent requests.

Affected context

The vulnerability occurs in deployments of SourceCodester Class and Exam Timetabling System 1.0 where the /delete_teacher.php endpoint accepts an ID parameter and incorporates it into a database query without adequate query parameterization. Risk depends on the endpoint being reachable over the network and on the application failing to enforce sufficient authorization and input-handling controls.

Exploit preconditions

  • Attack surface: The remotely accessible /delete_teacher.php endpoint
  • Required access: Network access to the application; authentication requirements depend on the deployment
  • Trigger point: Processing the ID argument in a teacher-deletion request
  • Why exploitation is possible: Attacker-controlled input may reach a database query without reliable separation between data and SQL syntax

Why this happens

The underlying bug is an injection flaw in which external input is incorporated into a SQL statement as executable query syntax rather than being handled strictly as data. This maps primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command, commonly known as SQL injection. The broader CWE-74 classification reflects the failure to neutralize special elements within an interpreted command language.

Potential impact

  • Unauthorized reading of application or database records
  • Modification or deletion of stored timetable and teacher data
  • Bypass of intended database query restrictions
  • Exposure of sensitive information held by the application
  • Further compromise could occur if the database account has excessive privileges

General mitigation guidance

Mitigation generally focuses on ensuring that database commands treat request values as data rather than executable SQL.

Common defensive patterns include:

  • Using parameterized queries or prepared statements for every database operation
  • Applying allowlisted type and range validation to identifier parameters
  • Enforcing authorization checks before destructive actions
  • Using database accounts with only the permissions required by the application
  • Avoiding detailed database errors in responses and logs exposed to users
  • Maintaining centralized input-handling and database-access policies

How teams detect issues like this

Organizations commonly detect SQL injection risks through:

  • Static analysis rules identifying string concatenation or interpolation in SQL construction
  • Code review checks for unparameterized query calls and missing authorization around delete operations
  • Dynamic application testing that supplies unexpected input types and observes database error behavior
  • Web application firewall or API policy rules monitoring anomalous request patterns
  • Database monitoring for unusual query structures, deletion volume, or access to unrelated tables

Automated security review tools may help identify unsafe query construction, but findings should be validated against application behavior and authorization requirements.

Sources

SourceLink
github.comgithub.com/justconter/cve/issues/10
vuldb.comvuldb.com/cve/CVE-2026-86208
vuldb.comvuldb.com/submit/896588
vuldb.comvuldb.com/vuln/399343
vuldb.comvuldb.com/vuln/399343/cti
sourcecodester.comsourcecodester.com/

Frequently asked

questions

Yes. The affected endpoint is described as remotely reachable, although practical exploitability depends on network exposure, authentication, authorization, and deployment configuration.

Not necessarily. The available description does not establish an authentication requirement; access to the endpoint and any applicable authorization controls determine the effective prerequisite.

Use parameterized database queries, validate the ID value as an expected identifier, and require explicit authorization before performing the deletion.

Enforce secure database-access patterns in shared libraries and code review, apply least-privilege database permissions, and combine static analysis with runtime monitoring and security testing.

Find out what's already
exploitable in your codebase.