CVE-2026-1176
SQL Injection in itsourcecode School Management System Allows Remote Exploit
Publication date: 2026-01-19
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| itsourcecode | school_management_system | 1.0 |
Helpful Resources
Exploitability
| 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 Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-1176 is a critical SQL injection vulnerability in itsourcecode School Management System version 1.0, specifically in the file /subject/index.php. The vulnerability occurs because the application does not properly sanitize or validate the 'id' parameter, allowing attackers to inject malicious SQL code remotely without authentication. This enables attackers to manipulate database queries, potentially leading to unauthorized data access, modification, or disruption of the system. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, full system control by attackers, and potential service disruption. It threatens the confidentiality, integrity, and availability of the system and its data, which can compromise business continuity and system security. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'id' parameter in HTTP GET requests to the /subject/index.php file for SQL injection flaws. One can use tools like sqlmap to automate detection, for example: sqlmap -u "http://target/subject/index.php?id=11" --technique=T --dbms=MySQL. Additionally, manual testing can be done by injecting payloads such as '11 AND (SELECT SLEEP(5))' to observe time delays indicating a time-based blind SQL injection. Attackers also use Google dorking with queries like 'inurl:subject/index.php' to identify vulnerable targets. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected product with an alternative solution, as no vendor patches are available. Additionally, implement prepared statements with parameter binding to separate SQL code from user input, enforce strict input validation ensuring parameters like 'id' are numeric, and minimize database user permissions to avoid high-privilege accounts for routine operations. Conduct regular security audits to detect and remediate vulnerabilities promptly. [1, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not contain information regarding the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.