CVE-2026-3765
SQL Injection in itsourcecode University Management System /att_single_view.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 | university_management_system | 1.0 |
Helpful Resources
Exploitability
| 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 Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-3765 is a critical SQL injection vulnerability found in itsourcecode University Management System version 1.0, specifically in the file /att_single_view.php. The vulnerability arises from improper handling of the dt parameter, which is manipulated to inject malicious SQL code. This occurs because the application directly incorporates the dt parameter into SQL queries without proper input validation or sanitization, allowing attackers to alter the intended SQL commands.
The flaw is classified under CWE-89 and can be exploited remotely without any authentication, making it highly accessible to attackers. Exploitation techniques include Boolean-based blind injection, error-based injection, time-based blind injection, and UNION-based injection.
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized database access, leakage of sensitive data, tampering with or deletion of data, and potentially gaining full system control. Attackers can also cause service interruptions, affecting the availability of the system.
Since exploitation does not require authentication, the system is highly vulnerable to remote attacks. The confidentiality, integrity, and availability of the system are all at risk.
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 vulnerability can be detected by identifying the presence of the vulnerable file and parameter in the system or network traffic. Specifically, the vulnerable endpoint is `/att_single_view.php` with the `dt` parameter being manipulated.'}, {'type': 'paragraph', 'content': 'One method to detect vulnerable targets is by using Google dorking with the query: `inurl:att_single_view.php`.'}, {'type': 'paragraph', 'content': 'For active testing, tools like sqlmap can be used to test the `dt` parameter for SQL injection by running commands such as:'}, {'type': 'list_item', 'content': 'sqlmap -u "http://target/att_single_view.php?dt=2021-04-11" --batch --dbs'}, {'type': 'list_item', 'content': 'sqlmap -u "http://target/att_single_view.php?dt=2021-04-11\' AND 1=1 --batch"'}, {'type': 'paragraph', 'content': 'These commands attempt to exploit the SQL injection vulnerability by injecting payloads into the `dt` parameter and enumerating databases or confirming injection.'}] [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Replace the affected component or upgrade to a version without the vulnerability if available.
- Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection.
- Apply strict input validation and filtering on the `dt` parameter to ensure it conforms to expected formats.
- Minimize database user permissions by avoiding high-privilege accounts for routine database operations.
- Conduct regular security audits to detect and fix vulnerabilities promptly.