SECURITYHIGHCVE-2026-16154

CVE-2026-16154: SQL Injection in SourceCodester Timetabling Room Management

A second SQL injection vulnerability in SourceCodester Class and Exam Timetabling System 1.0 has been disclosed, this time affecting the /edit_room1.php...

Dylan H.

Security Team

July 19, 2026
2 min read
CVE-2026-16154: SQL Injection in SourceCodester Timetabling Room Management

Affected Products

  • SourceCodester Class and Exam Timetabling System 1.0

Executive Summary

CVE-2026-16154 is a SQL injection vulnerability in SourceCodester Class and Exam Timetabling System 1.0, affecting the /edit_room1.php endpoint. This is a companion to CVE-2026-16152, which targets a related endpoint (/edit_rooma.php). Both vulnerabilities share the same root cause — unsanitized use of the ID GET/POST parameter in SQL queries — and both carry a CVSS score of 7.3 (High) with a public exploit already released.

CVSS Score: 7.3 (High)


Vulnerability Details

FieldValue
CVE IDCVE-2026-16154
CVSS Score7.3 (High)
CWECWE-89: SQL Injection
Attack VectorNetwork (Remote)
Privileges RequiredLow
User InteractionNone
Exploit AvailableYes (public)

Affected Component

The vulnerability is present in the /edit_room1.php file within SourceCodester Class and Exam Timetabling System version 1.0. The ID parameter is not properly sanitized before being included in database queries, allowing attackers to append arbitrary SQL directives.


Relationship to CVE-2026-16152

These two CVEs represent a pattern of insecure coding across the same application. When one endpoint in an application is found vulnerable to SQL injection, similar endpoints built with the same code patterns are often equally susceptible. Organizations using this software should treat both vulnerabilities as part of a broader systemic issue rather than isolated bugs.


Impact

A remote attacker exploiting this vulnerability could:

  • Extract database contents including room records, user credentials, and scheduling data
  • Manipulate scheduling data to disrupt exam and class timetables
  • Escalate privileges if the database account has elevated permissions
  • Chain with other vulnerabilities in the same application for deeper access

Remediation

  1. Restrict access to /edit_room1.php at the network perimeter or web server level
  2. Implement parameterized queries or prepared statements throughout the application
  3. Audit all similar endpoints in the codebase — the pattern likely repeats across other edit_*.php pages
  4. Apply the principle of least privilege to the database account used by this application
  5. Monitor for active exploitation using WAF rules targeting SQL injection patterns on this application

References