CVE-2026-0851
SQL Injection in code-projects Online Music Site AdminAddUser.php
Publication date: 2026-01-12
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 |
|---|---|---|
| code-projects | online_music_site | 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-0851 is a SQL injection vulnerability in version 1.0 of the Online Music Site project, specifically in the AdminAddUser.php file. The vulnerability occurs because the txtusername parameter is directly used in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code. This enables attackers to manipulate SQL queries, execute unauthorized database operations, and potentially gain full control over the system without needing authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, and service disruption. Attackers can execute arbitrary SQL commands remotely without authentication, potentially compromising the confidentiality, integrity, and availability of the system. This poses severe risks to system security and business continuity. [1, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'txtusername' parameter in the /Administrator/PHP/AdminAddUser.php file for SQL injection. A common method is to use a time-based blind SQL injection payload that causes a delay in the response if the system is vulnerable. For example, sending a POST request with the payload: txtusername=111' AND (SELECT 2924 FROM (SELECT(SLEEP(5)))knll) AND 'aZyx'='aZyx will cause a 5-second delay if the vulnerability exists. Additionally, attackers may be identified by searching for the vulnerable URL using Google dorking with queries like "inurl:Administrator/PHP/AdminAddUser.php". No specific network commands are provided, but testing the parameter with injection payloads and monitoring response times is effective. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Applying strict input validation and filtering on the 'txtusername' parameter to ensure inputs conform to expected formats. 3) Minimizing database user permissions by avoiding the use of high-privilege accounts (such as root or admin) for routine database operations. Since no patches or alternative products have been officially recommended, these coding and configuration changes are critical to protect system integrity. [1, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized attackers to perform SQL injection attacks, potentially leading to unauthorized database access, data leakage, and data tampering. Such impacts on confidentiality, integrity, and availability of data could result in non-compliance with data protection standards and regulations like GDPR and HIPAA, which require safeguarding sensitive data against unauthorized access and ensuring data integrity. Therefore, exploitation of this vulnerability could compromise compliance with these regulations. [1, 3]