/

CVE-2026-13526

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in Class Timetabling System

CVE-2026-13526

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

The Class and Exam Timetabling System 1.0 contains an SQL injection flaw in the /edit_class.php endpoint via the ID parameter.

An attacker sending crafted requests to this parameter can manipulate database queries remotely, potentially reading or altering sensitive scheduling and user data.

Affected context

The vulnerability arises in the web-based Class and Exam Timetabling System when handling the ID parameter in /edit_class.php.

It is most relevant in deployments where user-supplied request parameters are interpolated directly into SQL statements without robust validation or parameterization.

Risk increases when the application connects to the database with high privileges or is exposed to untrusted networks such as the public internet.

Exploit preconditions

  • Attack surface: HTTP requests to the /edit_class.php endpoint of the timetabling system.
  • Required access: Network access to the web application; no special local access is typically required.
  • Trigger point: Submission of crafted ID values in GET or POST requests that are used to build SQL queries.
  • Why exploitation is possible: The application constructs SQL statements by concatenating or directly embedding the ID parameter without using prepared statements or proper escaping, allowing attackers to alter query structure.

Why this happens

This issue stems from dynamically building SQL queries with untrusted input and failing to enforce strict separation between data and code.

The ID parameter from HTTP requests is treated as trusted and directly inserted into SQL, mapping to CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection').

At a broader level, it reflects CWE-74: Improper Neutralization of Special Elements in Output, where special characters in user-controlled input are not neutralized before being interpreted by the database engine.

Potential impact

  • Attackers may read timetable and class information beyond their authorization.
  • Attackers could modify or delete class, exam, and user records, disrupting scheduling operations.
  • Attackers can potentially escalate privileges by altering authentication or role data.
  • Attackers may exfiltrate sensitive student or staff information stored in the database.
  • In some configurations, attackers could execute database-specific functions that impact availability or integrity.

General mitigation guidance

Effective mitigation focuses on eliminating direct inclusion of untrusted input in SQL statements and reducing database privileges.

Common defensive patterns include:

  • Using parameterized queries or prepared statements for all database interactions.
  • Applying strict input validation on identifier parameters, enforcing expected formats (e.g., numeric IDs).
  • Limiting database account privileges so the application can only perform necessary operations.
  • Centralizing data access logic to avoid ad hoc query construction in presentation-layer scripts.
  • Adopting secure coding guidelines that forbid concatenated SQL and encourage ORM or query builder usage.

How teams detect issues like this

Organizations can detect SQL injection risks through:

  • Static analysis rules that flag string concatenation in SQL execution calls and direct usage of request parameters in queries.
  • Manual code reviews focusing on data access layers, looking for unparameterized queries and unchecked user input.
  • Runtime monitoring for anomalous query patterns, such as queries containing typical injection tokens or unexpected joins.
  • Security testing, including automated scanners and targeted penetration tests, to probe parameters like ID for injection behavior.
  • Policy enforcement in CI/CD pipelines requiring prepared statements and rejecting risky patterns before deployment.

Sources

SourceLink
github.comgithub.com/yuanyuandechen/vul/issues/2
vuldb.comvuldb.com/cve/CVE-2026-13526
vuldb.comvuldb.com/submit/840550
vuldb.comvuldb.com/vuln/374534
vuldb.comvuldb.com/vuln/374534/cti
sourcecodester.comsourcecodester.com/

Frequently asked

questions

Yes, if the timetabling system is exposed to the internet or any untrusted network, an attacker can send crafted HTTP requests to /edit_class.php and attempt SQL injection.

The attacker generally needs only network access to the web application; no valid credentials may be required if the vulnerable endpoint is reachable without authentication.

The safest approach is to use parameterized queries or prepared statements for the ID parameter, enforce strict validation on its format, and ensure the database account holds only minimal privileges required by the application.

Adopt a development standard that forbids dynamic SQL string concatenation, use ORMs or query builders configured for parameterized access by default, enforce input validation, and integrate static analysis and security testing into the build pipeline to catch injection patterns early.

Find out what's already
exploitable in your codebase.