/

CVE-2026-86225

Severity:

HIGH RISK

(7.3)

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

CVE-2026-86225

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Unauthorized database access and 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 SQL injection vulnerability in the Class and Exam Timetabling System allows attacker-controlled input in the room_name parameter to influence database queries.

Because the affected administrative endpoint may be reachable remotely, an attacker could potentially read, alter, or otherwise interact with database content when query construction is not safely parameterized.

Affected context

The vulnerability occurs in the administrative room-management functionality of SourceCodester Class and Exam Timetabling System 1.0, specifically in /admin/modal_add_room.php. It becomes risky when the room_name value is incorporated into a mysqli_query operation without adequate parameterization, and when the endpoint is accessible to an attacker through the application's deployed interface.

Exploit preconditions

  • Attack surface: The remotely reachable administrative room-management endpoint
  • Required access: Access sufficient to submit input to the affected functionality; the exact authentication requirement depends on deployment controls
  • Trigger point: Processing the room_name argument in /admin/modal_add_room.php
  • Why exploitation is possible: User-controlled input may affect SQL query structure when it is concatenated into database operations rather than handled as data through a parameterized interface

Why this happens

The underlying bug is an injection flaw caused by treating externally supplied room names as trusted SQL syntax. If application code constructs a query by combining input with SQL text and does not use parameter binding or equivalent escaping guarantees, special input can change the intended meaning of the query.

This maps primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'). CWE-74, Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection'), describes the broader class of interpreting untrusted data as commands for another component.

Potential impact

  • An attacker may read database records beyond the intended room-management data.
  • An attacker could modify or delete database content, depending on database permissions and query context.
  • The application may experience unauthorized changes to timetabling or administrative information.
  • Sensitive credentials or configuration data stored in the database could be exposed.
  • Database availability could be affected through destructive or resource-intensive operations.

General mitigation guidance

Mitigation generally focuses on ensuring that user input remains data throughout database processing.

Common defensive patterns include:

  • Use parameterized queries or prepared statements for every database operation involving external input.
  • Apply allowlist-based validation appropriate for room names, while treating validation as a supplement rather than a replacement for parameter binding.
  • Avoid dynamically assembling SQL syntax from request values.
  • Restrict database accounts to the minimum permissions required by the application.
  • Separate administrative endpoints from public access and enforce authorization consistently.
  • Avoid exposing detailed database errors to users and log suspicious query or input-handling failures securely.

How teams detect issues like this

Organizations can look for SQL injection risks through:

  • Static analysis rules identifying string concatenation or interpolation inside mysqli_query calls.
  • Code review checks for database queries that accept request parameters without prepared statements.
  • Dynamic application testing that monitors error behavior and unexpected query effects using approved test inputs.
  • Web-application firewall or API policy rules for anomalous database-oriented request patterns.
  • Database audit logging that highlights unusual read volume, query structure, privilege use, or modification activity.

Automated security review tools may help identify unsafe query construction, but findings should be validated against the application's actual data flow and authorization model.

Sources

SourceLink
github.comgithub.com/justconter/_CVE/issues/6
vuldb.comvuldb.com/cve/CVE-2026-86225
vuldb.comvuldb.com/submit/897751
vuldb.comvuldb.com/vuln/399378
vuldb.comvuldb.com/vuln/399378/cti
sourcecodester.comsourcecodester.com/

Frequently asked

questions

The reported attack surface is remotely reachable, so exploitation may be possible over the network when the affected endpoint is exposed. Actual scope depends on routing, authentication, authorization, and deployment configuration.

The description does not establish a universal authentication requirement. Access to the room-management function, whether authenticated or exposed through a misconfigured deployment, is the key condition to evaluate.

Use prepared statements or parameterized queries for all database operations involving request data, and enforce authorization independently of input validation.

Adopt centralized database-access APIs, prohibit dynamic SQL construction from untrusted values, apply least-privilege database accounts, and include static analysis and security testing in the development process.

Find out what's already
exploitable in your codebase.