CVE-2026-3765

7.3

itsourcecode · University Management System

A SQL injection vulnerability in the University Management System 1.0 allows unauthenticated remote attackers to execute arbitrary SQL queries via the 'dt' parameter in /att_single_view.php.

Executive summary

The University Management System 1.0 is vulnerable to unauthenticated SQL injection, posing a critical risk of full database compromise and unauthorized data access.

Vulnerability

The application fails to properly sanitize the 'dt' parameter within the /att_single_view.php file before using it in SQL queries. This flaw allows an unauthenticated attacker to manipulate database queries to extract, modify, or delete sensitive information.

Business impact

Successful exploitation of this vulnerability can lead to a total loss of confidentiality, integrity, and availability of the database. Given the CVSS score of 7.3, this represents a high-severity threat that could result in the exfiltration of student and faculty data, leading to severe reputational damage and potential regulatory non-compliance.

Remediation

Immediate Action: As no official vendor patch is currently available, administrators should restrict access to the /att_single_view.php file or the entire application until the vendor provides a secure update.

Proactive Monitoring: Review web server access logs for anomalous requests containing SQL syntax patterns, such as UNION, SELECT, or SLEEP commands, targeting the 'dt' parameter.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block common SQL injection patterns specifically targeting GET parameters.

Exploitation status

Public Exploit Available: Yes — a published proof-of-concept exists in the researcher's GitHub issue report.

Analyst recommendation

This vulnerability presents a significant risk due to the ease of exploitation and the lack of required authentication. Organizations using this software must treat this as a high-priority issue, implement immediate WAF-based filtering, and seek to replace or isolate the vulnerable component until a formal patch is released by the vendor.

More itsourcecode CVEs

Sources

Originally found and disclosed by Fanchen_Meng (VulDB User), per the CVE Program record.