CVE-2026-3747
SQL Injection in itsourcecode University Management System /add_result.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
How can this vulnerability impact me? :
Exploiting this vulnerability enables unauthorized database access, data modification or deletion, and exposure of sensitive information.
Potential impacts include unauthorized database access, data leakage, data tampering, full system control, and service disruption.
These impacts pose severe risks to system security, data integrity, confidentiality, availability, and business continuity.
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-3747 is a critical SQL injection vulnerability found in itsourcecode University Management System version 1.0, specifically in the /add_result.php file.'}, {'type': 'paragraph', 'content': 'The vulnerability arises from improper handling of the "subject" parameter, which allows an attacker to inject malicious SQL code by manipulating this input.'}, {'type': 'paragraph', 'content': 'This flaw is classified under CWE-89, meaning the system constructs SQL commands using externally influenced input without proper neutralization of special characters, enabling modification of the intended SQL query.'}, {'type': 'paragraph', 'content': 'The attack can be launched remotely without any authentication, making it highly accessible to attackers.'}, {'type': 'paragraph', 'content': 'A proof-of-concept exploit is publicly available, demonstrating how the injection can be performed, including time-based blind SQL injection techniques.'}] [1, 3]
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 /add_result.php endpoint for SQL injection via the subject parameter. A time-based blind SQL injection test can be performed by sending a specially crafted POST request with a payload that causes a delay if the vulnerability exists.'}, {'type': 'list_item', 'content': "Use a POST request with the payload: subject=DBMS' AND (SELECT 8547 FROM (SELECT(SLEEP(5)))rnqp) AND 'nDpj'='nDpj to check for a delay indicating vulnerability."}, {'type': 'list_item', 'content': 'Use tools like curl or sqlmap to automate detection of SQL injection on the /add_result.php file targeting the subject parameter.'}, {'type': 'list_item', 'content': 'Search for vulnerable targets using Google dorking with the query: inurl:add_result.php.'}] [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing secure coding practices to prevent SQL injection by properly handling the subject parameter.
- Use prepared statements with parameter binding to separate SQL code from user input.
- Implement strict input validation and filtering to ensure the subject parameter conforms to expected formats.
- Minimize database user permissions by avoiding use of high-privilege accounts like root or admin for routine database operations.
- Conduct regular security audits to detect and remediate vulnerabilities promptly.
If possible, replace the affected component or upgrade to a version without this vulnerability, as no known mitigations or countermeasures have been identified.