/

CVE-2026-11486

Severity:

HIGH RISK

(7.3)

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

CVE-2026-11486

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Database Compromise and Data Exfiltration

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

An SQL injection flaw in SourceCodester Class and Exam Timetabling System 1.0 allows unsanitized user input in the sy parameter of /archive1.php to be embedded directly into database queries.

When attackers can send crafted requests to this endpoint, they may manipulate or extract data from the backend database over the network.

Affected context

The vulnerability occurs in deployments of SourceCodester Class and Exam Timetabling System 1.0 that expose the /archive1.php script over HTTP(S).

It is relevant where:

  • The sy parameter is accepted from GET/POST requests and passed into SQL statements.
  • Database access is performed with dynamically constructed query strings.
  • There is no consistent parameterization or robust input handling for this specific code path.

In such contexts, user-controlled input can directly influence SQL commands executed by the application.

Exploit preconditions

  • Attack surface: Network-accessible web interface exposing /archive1.php.
  • Required access: Ability to send HTTP requests to the application; may be unauthenticated if the page is public.
  • Trigger point: Submission of a specially crafted sy parameter value as part of the request.
  • Why exploitation is possible: The sy argument is incorporated into SQL queries without proper parameterization or escaping, enabling attackers to alter the structure of the executed SQL.

Why this happens

This vulnerability stems from building SQL queries by concatenating or interpolating user input into query strings without using parameterized statements or rigorous input handling.

The behavior aligns with CWE-89: Improper Neutralization of Special Elements used in an SQL Command, where metacharacters such as quotes and operators are not correctly handled before execution.

It is also related to CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component, since the tainted input flows from the HTTP layer into the database engine, which treats the data as part of executable SQL rather than as a literal value.

Potential impact

  • Attackers may read or enumerate sensitive data stored in the database.
  • They could modify, insert, or delete timetabling and user-related records.
  • They may alter authentication or authorization data to escalate privileges.
  • They might cause availability issues by triggering destructive or expensive queries.
  • In some configurations, they can potentially chain this into further compromise of the underlying host or adjacent systems.

General mitigation guidance

Effective mitigation focuses on eliminating direct string concatenation in SQL and reducing trust in user-provided data across the application:

  • Prefer parameterized queries or prepared statements to separate SQL logic from data values.
  • Apply strict server-side validation and whitelisting for parameters like sy, constraining them to expected formats (e.g., specific year or code patterns).
  • Centralize database access patterns so that secure query construction is enforced consistently.
  • Minimize database privileges assigned to the application's account, limiting operations to only what the application legitimately needs.
  • Consider adding defense-in-depth controls such as web input normalization and generic error handling that avoids leaking database details.

How teams detect issues like this

Detection efforts can combine code-level analysis with runtime observations:

  • Use static analysis or secure code review to flag dynamic SQL assembly where request parameters (e.g., $_GET['sy'], $_POST['sy']) are concatenated into queries.
  • Look for repeated patterns of SELECT, UPDATE, or DELETE statements built with string interpolation instead of bound parameters.
  • Implement application- or database-level logging to detect anomalous query patterns, including unexpected operators, comment markers, or tautological conditions.
  • Integrate automated security testing (such as generic SQL injection test suites) into CI/CD pipelines so that changes to PHP scripts like /archive1.php are regularly assessed.

Sources

SourceLink
github.comgithub.com/ssaaaa1234/cve/issues/1
vuldb.comvuldb.com/cve/CVE-2026-11486
vuldb.comvuldb.com/submit/834111
vuldb.comvuldb.com/vuln/369106
vuldb.comvuldb.com/vuln/369106/cti
sourcecodester.comsourcecodester.com/

Frequently asked

questions

Exploitability depends on whether /archive1.php is reachable from untrusted networks; if it is publicly accessible on the internet, any remote user who can send HTTP requests may be able to attempt exploitation.

Not necessarily. If the vulnerable endpoint is accessible without authentication, exploitation can occur anonymously; if it is behind a login, an attacker would first need at least low-privileged access.

The most robust fix is to refactor all affected database interactions to use parameterized queries or prepared statements, ensuring that user input is always treated as data, not executable SQL, and pairing this with strict server-side validation.

Adopting secure coding standards that prohibit dynamic SQL concatenation, enforcing code review checks for query construction, and using automated static analysis to flag unsafe patterns help prevent new SQL injection flaws from being introduced.

Find out what's already
exploitable in your codebase.