CVE-2026-5553
SQL Injection in itsourcecode Online Cellphone 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_cellphone_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-5553 is a SQL injection vulnerability in the Online Cellphone System version 1.0, specifically in the /cp/available.php file. The issue arises because the 'name' parameter in a multipart/form-data POST request is used directly in SQL queries without proper sanitization or validation. This allows attackers to inject malicious SQL code remotely without needing authentication.
Attackers can exploit this vulnerability using different SQL injection techniques such as boolean-based blind SQL injection, error-based SQL injection, and time-based blind SQL injection. These techniques enable them to manipulate database queries to extract, modify, or delete data.
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized access to the database, data leakage, data tampering, and potentially full control over the affected system. Attackers can disrupt services or manipulate sensitive information stored in the database.
- Unauthorized database access
- Data leakage of sensitive information
- Data tampering or corruption
- Potential full system control
- Service disruption
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The vulnerability can be detected by testing the /cp/available.php endpoint for SQL injection via the 'name' parameter using multipart/form-data POST requests.
Three types of SQL injection techniques can be used for detection: boolean-based blind SQL injection, error-based SQL injection, and time-based blind SQL injection.
Tools like sqlmap can be used to confirm the vulnerability by executing crafted POST requests targeting the 'name' parameter.
- Use sqlmap with a command similar to: sqlmap -u "http://target/cp/available.php" --data="name=TEST&foodid=1&address=1&contact=1&oqty=1&otype=1&datep=1" --method=POST --level=5 --risk=3
- Manually test with payloads such as boolean-based blind SQL injection using MySQL RLIKE operator, error-based SQL injection exploiting MySQL error messages, or time-based blind SQL injection using MySQL SLEEP function in the 'name' parameter.
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.
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 for application access.
Conduct regular security audits to detect and fix vulnerabilities promptly.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The CVE-2026-5553 vulnerability allows attackers to perform SQL injection attacks that can lead to unauthorized database access, data leakage, data tampering, and full system control. Such unauthorized access and potential exposure or alteration of sensitive data can result in non-compliance with common standards and regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive information.
Failure to remediate this vulnerability may lead to breaches of confidentiality, integrity, and availability of data, which are core requirements under these regulations. This can result in legal penalties, reputational damage, and loss of trust.