CVE-2026-2011
SQL Injection in itsourcecode Student Management System Enrollment Controller
Publication date: 2026-02-06
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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': "CVE-2026-2011 is a SQL injection vulnerability in the itsourcecode Student Management System version 1.0, specifically in the file /ramonsys/enrollment/controller.php. The vulnerability occurs because the application does not properly sanitize or validate the 'id' parameter before using it in SQL queries. This allows an attacker to inject malicious SQL code remotely without needing to authenticate, enabling unauthorized manipulation of the database."}] [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized database access, leakage of sensitive data, data tampering, full system control by attackers, and service interruptions. Because exploitation requires no authentication, attackers can remotely manipulate SQL queries to compromise the confidentiality, integrity, and availability of the system, severely affecting system security and business continuity.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': "This SQL injection vulnerability can be detected by testing the vulnerable parameter 'id' in the URL for injection flaws. A proof-of-concept payload uses a time-based blind SQL injection technique to confirm the vulnerability by causing a delay in the response."}, {'type': 'paragraph', 'content': 'One suggested command to test this vulnerability is using sqlmap, an automated SQL injection tool, with the following example command:'}, {'type': 'list_item', 'content': 'python sqlmap.py --random-agent --batch -u "http://192.168.174.128:9006/ramonsys/enrollment/controller.php?action=confirmEnrol&id=4" --dbms=mysql -p id --current-db'}, {'type': 'paragraph', 'content': 'Alternatively, a manual test can be performed by appending a payload to the URL to check for time delays, such as:'}, {'type': 'list_item', 'content': 'action=confirmEnrol&id=4 AND (SELECT 5737 FROM (SELECT(SLEEP(5)))YlSL)'}, {'type': 'paragraph', 'content': 'If the response is delayed by approximately 5 seconds, it indicates a successful SQL injection.'}, {'type': 'paragraph', 'content': 'Additionally, vulnerable targets can be identified using Google dorking with the query: inurl:ramonsys/enrollment/controller.php'}] [2, 3]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'Immediate mitigation steps for this SQL injection vulnerability include:'}, {'type': 'list_item', 'content': 'Use prepared statements and parameter binding to separate SQL code from user input, preventing injection.'}, {'type': 'list_item', 'content': "Implement strict input validation and filtering to ensure inputs conform to expected formats, such as numeric patterns for the 'id' parameter."}, {'type': 'list_item', 'content': 'Minimize database user permissions by avoiding the use of high-privilege accounts for routine database operations.'}, {'type': 'list_item', 'content': 'Conduct regular security audits to detect and address vulnerabilities promptly.'}] [2]