CVE-2026-5534
SQL Injection in itsourcecode Online Enrollment System Parameter Handler
Publication date: 2026-04-05
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?
CVE-2026-5534 is a critical SQL injection vulnerability in the Online Enrollment System version 1.0, specifically in the file /sms/user/index.php?view=edit&id=10. The vulnerability arises from improper handling of the USERID parameter, which is used directly in SQL queries without proper input validation or sanitization.
This flaw allows attackers to inject malicious SQL code remotely, without requiring user authentication. Exploiting this vulnerability can lead to unauthorized access to the database, data leakage, modification or deletion of data, and potentially full system compromise or service disruption.
The vulnerability was demonstrated using a time-based blind SQL injection payload targeting the USERID parameter, confirming the system's susceptibility to such attacks.
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data stored in the database, data leakage, and unauthorized modification or deletion of data.
Attackers can exploit this flaw to disrupt services or potentially gain full control over the affected system, leading to service downtime and loss of data integrity.
Since exploitation does not require authentication, any remote attacker can attempt to exploit this vulnerability, increasing the risk exposure.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The CVE-2026-5534 vulnerability can be detected by testing the USERID parameter in the URL /sms/user/index.php?view=edit&id=10 for SQL injection. A common method is to use time-based blind SQL injection payloads, such as injecting USERID=10 AND (SELECT 7421 FROM (SELECT(SLEEP(5)))hRgt) and observing if the response is delayed, indicating successful injection.
Tools like sqlmap can be used to automate detection by injecting various payloads and analyzing the responses for signs of SQL injection.
- Example command using sqlmap: sqlmap -u "http://target/sms/user/index.php?view=edit&id=10" --data="USERID=10" --technique=T --time-sec=5
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Use prepared statements with parameter binding to separate SQL code from user input, preventing SQL injection.
- Implement strict input validation and filtering to ensure inputs conform to expected formats.
- Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts like root or admin for routine operations.
- Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in the Online Enrollment System 1.0 allows unauthorized database access, data leakage, modification, or deletion. Such unauthorized access and potential data breaches can lead to non-compliance with data protection regulations like GDPR and HIPAA, which require the protection of personal and sensitive data against unauthorized access and breaches.
Failure to remediate this vulnerability could result in exposure of personal data, violating confidentiality and integrity requirements mandated by these standards, potentially leading to legal and financial consequences.