CVE-2026-3944
SQL Injection in itsourcecode University Management System /att_add.php
Publication date: 2026-03-11
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-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-3944 is a critical SQL injection vulnerability found in itsourcecode University Management System version 1.0, specifically in the file /att_add.php.'}, {'type': 'paragraph', 'content': 'The vulnerability arises from improper handling of the "Name" parameter, which allows an attacker to inject malicious SQL code due to inadequate neutralization of special characters in the input.'}, {'type': 'paragraph', 'content': 'This issue corresponds to CWE-89, where externally influenced input is used to construct SQL commands without proper sanitization, leading to unauthorized modification of the SQL query.'}, {'type': 'paragraph', 'content': 'The attack can be initiated remotely without any authentication, making it easy to exploit.'}] [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, and full system compromise.
Attackers can manipulate, delete, or expose sensitive information stored in the database.
It can also cause service disruption and impact the confidentiality, integrity, and availability of the system.
The exploit requires no authentication and is easy to perform, increasing the risk of exploitation.
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 testing the /att_add.php endpoint for SQL injection in the 'name' parameter. One method is to use time-based blind SQL injection payloads to confirm the injection point."}, {'type': 'paragraph', 'content': "A proof-of-concept payload to test this vulnerability is: name=1111' AND (SELECT 1089 FROM (SELECT(SLEEP(5)))lNwb) AND 'Ozlo'='Ozlo&stid=1111&sub=Add student"}, {'type': 'paragraph', 'content': 'You can use tools like curl or Burp Suite to send POST requests with this payload to observe if the response is delayed, indicating a successful injection.'}, {'type': 'list_item', 'content': 'Example curl command to test the vulnerability: curl -X POST -d "name=1111\' AND (SELECT 1089 FROM (SELECT(SLEEP(5)))lNwb) AND \'Ozlo\'=\'Ozlo&stid=1111&sub=Add student" http://targetsite/att_add.php'}, {'type': 'list_item', 'content': 'Use Google dorking to find potentially vulnerable targets by searching for URLs containing "att_add.php".'}] [1, 2]
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, preventing injection.
Strict input validation and filtering should be applied to ensure inputs conform to expected formats.
Minimize database user permissions by avoiding the use of high-privilege accounts such as root or admin for routine database operations.
Conduct regular security audits of code and systems to detect and remediate vulnerabilities promptly.
Since no known countermeasures or patches are currently available, it is recommended to replace the affected product with an alternative solution if possible.