CVE-2026-3760
SQL Injection in itsourcecode University Management System /view_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-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
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 requests to the vulnerable endpoint `/view_result.php` that include the `seme` parameter. One method is to use Google dorking with the query `inurl:view_result.php` to find potentially vulnerable targets.'}, {'type': 'paragraph', 'content': "Testing for SQL injection can be done by sending specially crafted payloads to the `seme` parameter and observing the response. For example, a time-based blind SQL injection payload like `seme=1st' AND (SELECT SLEEP(5))-- -` can be used to detect delays indicating vulnerability."}, {'type': 'paragraph', 'content': 'Using automated tools such as sqlmap with the target URL and the `seme` parameter can confirm the presence of the SQL injection vulnerability.'}, {'type': 'list_item', 'content': 'Google dork: `inurl:view_result.php`'}, {'type': 'list_item', 'content': "Manual test payload example: `seme=1st' AND (SELECT 3379 FROM (SELECT(SLEEP(5)))BJJz) AND 'iITg'='iITg`"}, {'type': 'list_item', 'content': 'Automated test: Use sqlmap targeting the URL with the `seme` parameter'}] [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected product if possible, as no official patches or countermeasures are currently available.
Implement secure coding practices such as using prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input.
Apply strict input validation and filtering on the `seme` parameter to ensure it conforms to expected formats and does not contain malicious content.
Minimize database user permissions by avoiding the use of high-privilege accounts (e.g., root or admin) for routine database operations.
Conduct regular security audits and vulnerability assessments to detect and address issues promptly.
Can you explain this vulnerability to me?
CVE-2026-3760 is a critical SQL injection vulnerability found in itsourcecode University Management System version 1.0, specifically in the file /view_result.php.
The vulnerability arises from improper handling of the seme parameter, which is used in constructing SQL queries without adequate sanitization or neutralization of special characters, leading to SQL injection.
This flaw allows an attacker to remotely execute arbitrary SQL commands without authentication, potentially compromising the confidentiality, integrity, and availability of the system.
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized database access, allowing attackers to retrieve sensitive information, modify or delete data, and potentially gain full control over the affected system.
The attack can be performed remotely without any authentication, increasing the risk of data leakage, data tampering, and service disruption.
Such exploitation threatens the confidentiality, integrity, and availability of the system and its data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know