CVE-2026-3767
SQL Injection in itsourcecode 1.0 /admin/teacher-attendance.php
Publication date: 2026-03-08
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 |
|---|---|---|
| angeljudesuarez | college_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?
[{'type': 'paragraph', 'content': "CVE-2026-3767 is a SQL injection vulnerability found in the College Management System version 1.0, specifically in the /admin/teacher-attendance.php file. The vulnerability occurs because the application does not properly sanitize or validate the 'teacher_id' input parameter before using it in SQL queries."}, {'type': 'paragraph', 'content': "This flaw allows an attacker, who must be authenticated, to inject malicious SQL code through the 'teacher_id' parameter. By doing so, the attacker can manipulate the database queries executed by the system."}, {'type': 'paragraph', 'content': 'Proof-of-concept attacks include time-based blind SQL injection and UNION-based SQL injection, which demonstrate how attackers can extract data or cause delays in the database response.'}] [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, allowing attackers to read sensitive data, modify or delete data, and potentially gain full control over the affected system.
This can result in data leakage, data tampering, disruption of services, and compromise of system security and business continuity.
Because the vulnerability can be exploited remotely by authenticated users, it poses a significant risk to the confidentiality, integrity, and availability of the system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
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 endpoint /admin/teacher-attendance.php, specifically targeting the 'teacher_id' parameter for injection attempts."}, {'type': 'paragraph', 'content': 'Example commands to detect the vulnerability include using time-based blind SQL injection payloads or UNION-based SQL injection payloads.'}, {'type': 'list_item', 'content': "Time-based blind SQL injection payload example: teacher_id=1' AND (SELECT 4428 FROM (SELECT(SLEEP(5)))hdLA) AND 'tmCC'='tmCC&submit=Search"}, {'type': 'list_item', 'content': "UNION-based SQL injection payload example: teacher_id=1' UNION ALL SELECT NULL,CONCAT(0x7176627171,0x736d6a6a594b527a72626b414f6b4d786f47505573467566704d6f6457487659484564446e574564,0x7176767171),NULL,NULL-- -&submit=Search"}, {'type': 'paragraph', 'content': "Additionally, automated tools like sqlmap can be used to test the endpoint with parameters targeting the 'teacher_id' parameter to confirm the presence of the vulnerability."}] [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input.
Strict input validation and filtering should be enforced to ensure inputs conform to expected formats, such as numeric validation for IDs.
Minimize database user permissions by avoiding the use of high-privilege accounts for routine operations.
Conduct regular security audits to detect and remediate vulnerabilities promptly.