CVE-2026-11472
Deferred Deferred - Pending Action
SQL Injection in Class and Exam Timetabling System

Publication date: 2026-06-08

Last updated on: 2026-06-08

Assigner: VulDB

Description
A vulnerability was determined in SourceCodester Class and Exam Timetabling System 1.0. This affects an unknown function of the file /index1.php. This manipulation of the argument Password causes sql injection. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-08
Last Modified
2026-06-08
Generated
2026-06-08
AI Q&A
2026-06-08
EPSS Evaluated
N/A
NVD
CVE-2026-11472
EUVD
EUVD-2026-35003
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-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.
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.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Compliance Impact

The SQL injection vulnerability in the Class and Exam Timetabling System allows unauthorized database access, data tampering, and sensitive information leakage. Such security flaws can lead to violations of data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive data against unauthorized access and breaches.

Failure to protect data integrity and confidentiality due to this vulnerability may result in non-compliance with these standards, potentially leading to legal penalties, reputational damage, and loss of trust.

Mitigating this vulnerability by implementing prepared statements, strict input validation, minimizing database permissions, and regular security audits is essential to maintain compliance with common data protection regulations.

Impact Analysis

Exploiting this vulnerability can lead to unauthorized access to the database, allowing attackers to tamper with data, leak sensitive information, disrupt services, or even gain control over the affected system.

Such impacts threaten system security and data integrity, potentially causing significant operational and reputational damage.

Executive Summary

This vulnerability is a SQL injection flaw found in the Class and Exam Timetabling System version 1.0, specifically in the /index1.php file. It occurs because the 'password' parameter is not properly validated, allowing attackers to inject malicious SQL code remotely without needing to log in or have authorization.

Attackers can exploit this vulnerability using various SQL injection techniques such as boolean-based blind, error-based, and time-based blind methods to manipulate database queries.

Detection Guidance

This SQL injection vulnerability in the /index1.php file can be detected by testing the 'password' parameter for SQL injection flaws using various techniques such as boolean-based blind, error-based, and time-based blind SQL injection.

You can use commands or tools that send crafted payloads to the 'password' parameter to observe the system's response and detect injection points.

  • Use curl or similar tools to send payloads like: curl 'http://target/index1.php?password=1' OR '1'='1'
  • Use sqlmap to automate detection: sqlmap -u "http://target/index1.php" --data="password=anything" --risk=3 --level=5
  • Observe for abnormal responses, delays, or error messages indicating SQL query manipulation.
Mitigation Strategies

Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection.

Additionally, apply strict input validation and filtering on the 'password' parameter to block malicious input.

Minimize database user permissions to limit the impact of a potential exploit.

Conduct regular security audits and patch the vulnerable system as soon as a fix is available.

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