CVE-2026-1701
SQL Injection in itsourcecode SMS 1.0 /enrollment/index.php Allows Remote Exploit
Publication date: 2026-01-30
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-1701 is a SQL injection vulnerability in the itsourcecode Student Management System version 1.0, specifically in the /enrollment/index.php file. The vulnerability occurs because the application does not properly sanitize or validate the 'id' parameter before using it in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, enabling unauthorized manipulation of database queries. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can allow attackers to gain unauthorized access to the database, leak sensitive information, modify or tamper with data, gain full control over the system, and cause service interruptions. This poses a severe threat to data confidentiality, integrity, and system availability, potentially disrupting business continuity. [1, 2, 3]
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 the /enrollment/index.php file for SQL injection. A practical approach is to use the sqlmap tool with a command like: python sqlmap.py --random-agent --batch -u "http://<target>/ramonsys/enrollment/index.php?view=viewsced&id=20004623" --dbms=mysql -p id --current-db. This command tests the 'id' parameter for SQL injection vulnerabilities against a MySQL database. Additionally, boolean-based blind, time-based blind, and UNION query payloads can be used to manually test the injection point. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements and parameter binding to separate SQL code from user input, preventing injection. 2) Implement strict input validation and filtering, ensuring inputs conform to expected formats such as numeric patterns for IDs. 3) Minimize database user permissions by avoiding high-privilege accounts like 'root' or 'admin' for routine operations. 4) Conduct regular security audits to identify and fix vulnerabilities promptly. Since no known countermeasures exist, replacing the affected product with a secure alternative is also suggested. [2, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows unauthorized access and manipulation of sensitive data through SQL injection, which can lead to data breaches and compromise confidentiality, integrity, and availability of information. Such security failures can result in non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive data. Therefore, exploitation of this vulnerability could lead to violations of these regulations due to unauthorized data exposure and lack of adequate security controls. [2, 3]