CVE-2026-14771
Deferred Deferred - Pending Action

SQL Injection in Class and Exam Timetabling System

Publication date: 2026-07-05

Last updated on: 2026-07-06

Assigner: VulDB

Description
A flaw has been found in SourceCodester Class and Exam Timetabling System 1.0/1.php. The affected element is an unknown function of the file /edit_exam1.php. Executing a manipulation of the argument ID can lead to sql injection. It is possible to launch the attack remotely. The exploit has been published and may be used.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-05
Last Modified
2026-07-06
Generated
2026-07-26
AI Q&A
2026-07-06
EPSS Evaluated
2026-07-24
NVD
CVE-2026-14771
EUVD
EUVD-2026-41781

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
sourcecodester class_and_exam_timetabling_system 1.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-74 The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a flaw found in the SourceCodester Class and Exam Timetabling System version 1.0/1.php, specifically in an unknown function within the file /edit_exam1.php.

The issue arises from improper handling of the argument ID, which can be manipulated to perform an SQL injection attack.

This means an attacker can remotely exploit this vulnerability by injecting malicious SQL code through the ID parameter, potentially compromising the database.

The exploit has already been published and may be used by attackers.

Detection Guidance

This vulnerability can be detected by testing the 'id' parameter in the /edit_exam1.php file for SQL injection flaws. Common methods include sending crafted input to observe if the application behaves unexpectedly or returns database errors.

  • Use tools like sqlmap to automate detection, for example: sqlmap -u "http://targetsite/edit_exam1.php?id=1" --batch
  • Manually test with payloads such as ' OR '1'='1 or ' OR 1=1-- to see if the response changes or reveals database errors.
  • Monitor network traffic for suspicious requests targeting the 'id' parameter with SQL injection patterns.
Impact Analysis

This vulnerability can have serious impacts including unauthorized access to sensitive data, data modification, or deletion.

Because it allows SQL injection, an attacker could manipulate the database to extract confidential information, alter exam schedules, or disrupt the normal operation of the timetabling system.

The vulnerability has a high severity score (CVSS v3.1 Base Score 7.3), indicating it can lead to significant confidentiality, integrity, and availability impacts.

Compliance Impact

The vulnerability is a SQL injection flaw in the SourceCodester Class and Exam Timetabling System that allows remote attackers to manipulate the argument ID, potentially leading to unauthorized access or modification of data.

Such unauthorized access or data manipulation can impact compliance with data protection regulations like GDPR and HIPAA, which require the protection of personal and sensitive information from unauthorized access and breaches.

Therefore, exploitation of this vulnerability could lead to violations of these standards due to compromised confidentiality, integrity, and availability of data.

Mitigation Strategies

Immediate mitigation steps include:

  • Implement prepared statements with parameterized queries to prevent SQL injection.
  • Validate and sanitize all user inputs, especially the 'id' parameter.
  • Restrict database user permissions to the minimum necessary.
  • Conduct regular security audits and code reviews focusing on input handling.
  • If possible, apply patches or updates provided by the software vendor.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-14771. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart