CVE-2026-0852
SQL Injection in Online Music Site AdminUpdateUser.php Allows Remote Exploits
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-0852 is a SQL injection vulnerability in the AdminUpdateUser.php file of the Online Music Site version 1.0. The vulnerability occurs because the 'id' parameter is directly included in SQL queries without proper sanitization or validation. This allows attackers to inject malicious SQL code remotely, manipulating database queries to perform unauthorized operations such as accessing, modifying, or deleting data. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing attackers to gain unauthorized access to your database, leak sensitive information, modify or delete data, take full control of the system, and disrupt service availability. Exploitation requires no authentication and can be performed remotely, making it highly accessible and dangerous. [2, 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 vulnerable endpoint /Administrator/PHP/AdminUpdateUser.php for SQL injection via the 'id' parameter, which is passed via POST requests. Tools like sqlmap can be used to confirm exploitability and enumerate the database. A proof-of-concept POST request targeting this endpoint with parameters including 'id' can be crafted to test for injection. Additionally, Google dorking with queries such as inurl:Administrator/PHP/AdminUpdateUser.php can help identify vulnerable targets. Example command using sqlmap: sqlmap -u "http://target/mis/Administrator/PHP/AdminUpdateUser.php" --data="id=17&other_params=values" --risk=3 --level=5 [2, 3]
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, enforcing strict input validation and filtering to ensure inputs conform to expected formats, and minimizing database user privileges by avoiding the use of high-privilege accounts for routine operations. Since no known mitigations or countermeasures are identified, replacing the affected component with an alternative product is also suggested. Prompt remediation is critical to protect system security and data integrity. [1, 2, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows attackers to perform unauthorized database operations, including accessing, modifying, or deleting sensitive data, which can lead to breaches of confidentiality, integrity, and availability. Such breaches can result in non-compliance with data protection regulations like GDPR and HIPAA that require safeguarding personal and sensitive information. Therefore, this SQL injection flaw poses a significant risk to compliance with these standards by potentially exposing protected data and failing to maintain required security controls. [1, 2, 3]