CVE-2026-4632
SQL Injection in itsourcecode Online Enrollment System Parameter Handler
Publication date: 2026-03-24
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 |
|---|---|---|
| itsourcecode | online_enrollment_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-4632 is a critical SQL injection vulnerability found in the Online Enrollment System version 1.0, specifically in the file /sms/user/index.php?view=add. The issue arises because the 'name' parameter is directly used in SQL queries without proper input validation or sanitization."}, {'type': 'paragraph', 'content': 'This flaw allows attackers to inject malicious SQL code remotely without authentication, potentially leading to unauthorized database access, data leakage, data manipulation, full system control, and service disruption.'}, {'type': 'paragraph', 'content': "The vulnerability can be exploited using techniques such as Boolean-based blind SQL injection and time-based blind SQL injection by crafting specific payloads in the 'name' parameter."}] [1]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, data leakage, and unauthorized modification or deletion of data.
Attackers could gain full control over the affected system, potentially disrupting services and compromising business continuity.
Because exploitation requires no authentication, the risk of attack is high, making it critical to address immediately to protect data integrity and system stability.
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': 'The vulnerability can be detected by testing the vulnerable endpoint `/sms/user/controller.php?action=add` with crafted POST requests targeting the `name` parameter.'}, {'type': 'paragraph', 'content': 'Common detection methods include using SQL injection testing tools such as sqlmap to send payloads that exploit the improper handling of the `name` parameter.'}, {'type': 'list_item', 'content': "Example boolean-based blind SQL injection payload: `name=12%' OR NOT 4398=4398 #`"}, {'type': 'list_item', 'content': "Example time-based blind SQL injection payload: `name=12%' AND (SELECT SLEEP(5)) AND 'IHio'='IHio`"}, {'type': 'paragraph', 'content': 'A sample command using sqlmap would be to target the endpoint with a POST request including the vulnerable parameter, for example: `sqlmap -u "http://target/sms/user/controller.php?action=add" --data="name=12"` and then customize payloads to test for injection.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to ensure user input is not directly included in SQL queries.
Enforce strict input validation and filtering on the `name` parameter to ensure inputs conform to expected formats and reject malicious payloads.
Limit database user permissions to the minimum necessary, avoiding the use of high-privilege accounts such as `root` or `admin` for routine database operations.
Conduct regular security audits of the code and systems to detect and address vulnerabilities promptly.