/

CVE-2026-11482

Severity:

HIGH RISK

(7.3)

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

CVE-2026-11482

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Data Exposure and Database Compromise

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 flaw in SourceCodester Class and Exam Timetabling System 1.0 allows crafted input in the sy parameter of archive5.php to alter backend database queries.

Because the vulnerable endpoint is reachable remotely and exploit code is public, an attacker can manipulate or exfiltrate data when the application directly interpolates user-controlled values into SQL statements.

Affected context

The vulnerability occurs in the web-facing archive5.php component of the Class and Exam Timetabling System when handling the sy argument.

It is relevant in deployments where:

  • The application is exposed over a network (e.g., internet or intranet)
  • The sy parameter is accepted from HTTP requests and used in database queries
  • Server-side input validation or parameterization for this value is absent or incomplete

Real-world impact depends on database privileges granted to the application account and surrounding hardening controls.

Exploit preconditions

  • Attack surface: HTTP/S endpoint handling requests to archive5.php
  • Required access: Network access to the application (no prior authentication may be required, depending on deployment)
  • Trigger point: Supplying crafted values to the sy parameter so that they are concatenated into SQL queries
  • Why exploitation is possible: The application constructs SQL statements by combining user-controlled input with query strings without using prepared statements or proper escaping, enabling injection of additional SQL syntax

Why this happens

The underlying issue is improper neutralization of external input before it is used to build SQL queries, aligning with CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection').

The sy parameter appears to be inserted directly into SQL, likely through string concatenation or interpolation, without consistent use of parameterized queries or robust input handling.

This pattern combines aspects of CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component, as untrusted data flows into the database layer where it is interpreted as executable SQL rather than pure data.

Potential impact

  • Retrieval of sensitive or otherwise restricted data from the application database
  • Modification or deletion of timetable records or related academic data
  • Creation of new administrative or user accounts within the application data store
  • Corruption of scheduling information, potentially disrupting operational processes
  • Use of the database as a pivot point to explore other systems, depending on configuration and privileges

General mitigation guidance

Mitigation for this class of issue generally focuses on separating data from code at the database layer and limiting trust in user inputs:

  • Use parameterized queries or prepared statements for all database operations that involve user-controlled values, including sy
  • Apply strict server-side validation and normalization of inputs, constraining them to expected formats (e.g., integers, enumerated values)
  • Centralize data access logic so that query construction patterns are easier to audit and standardize
  • Configure database accounts with least-privilege permissions so that the application can only perform necessary operations
  • Introduce a consistent encoding and escaping strategy for any remaining dynamic query fragments that cannot be parameterized

How teams detect issues like this

Organizations can identify this vulnerability class through a combination of review and testing:

  • Static code analysis to flag direct string concatenation of request parameters into SQL statements or use of unsafe query-building APIs
  • Manual code review focusing on PHP scripts like archive5.php, tracing the flow of $_GET, $_POST, or other user inputs into database calls
  • Runtime or dynamic testing with web application scanners configured to probe parameters such as sy for SQL injection indicators
  • Logging and monitoring of database activity for anomalous queries, such as those containing unexpected operators or tautological predicates originating from web requests

Sources

SourceLink
github.comgithub.com/ssaaaa1234/cve/issues/5
vuldb.comvuldb.com/cve/CVE-2026-11482
vuldb.comvuldb.com/submit/834107
vuldb.comvuldb.com/vuln/369102
vuldb.comvuldb.com/vuln/369102/cti
sourcecodester.comsourcecodester.com/

Frequently asked

questions

Yes. The vulnerable parameter is exposed via an HTTP endpoint, so any attacker with network access to the application can attempt exploitation.

Not necessarily. Exploitability depends on how the application is configured; if archive5.php is accessible without login, then no authentication is required.

Replace all dynamic SQL construction involving user inputs with prepared statements or parameterized queries, and enforce strict input validation on parameters such as sy.

Adopt a development standard that forbids concatenating user input into SQL, use frameworks or libraries that default to parameterization, and integrate static analysis and security testing into the CI pipeline to catch injection patterns early.

Find out what's already
exploitable in your codebase.