CVE-2026-10171
SQL Injection in Online Music Site 1.0
Publication date: 2026-05-31
Last updated on: 2026-05-31
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-10171 is a SQL injection vulnerability found in the Online Music Site version 1.0, specifically in the AdminUpdateAlbum.php file. The vulnerability occurs because the "id" parameter is used directly in SQL queries without proper sanitization or validation.
This allows attackers to inject malicious SQL code remotely, potentially exploiting the system without needing login or authorization.
The types of SQL injection techniques that can be used include boolean-based blind, error-based, and time-based blind SQL injection.
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized access to the database, resulting in data leakage and data tampering.
Attackers may gain control over the system or disrupt services, causing significant operational and security issues.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the "id" parameter in the AdminUpdateAlbum.php file for SQL injection flaws. Since the vulnerability allows boolean-based blind, error-based, and time-based blind SQL injection techniques, you can use SQL injection testing tools or manual commands to detect it.
- Use sqlmap or similar automated tools targeting the vulnerable URL with the "id" parameter, for example: sqlmap -u "http://target/Administrator/PHP/AdminUpdateAlbum.php?id=1" --batch
- Manually test with payloads such as ' OR 1=1-- to see if the response changes, indicating SQL injection.
- Use time-based payloads like '1' OR SLEEP(5)-- to check for delayed responses.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Implement prepared statements with parameter binding to prevent direct injection of user input into SQL queries.
- Apply rigorous input validation and filtering on the "id" parameter to ensure only expected values are processed.
- Minimize database user permissions to limit the potential impact of an exploit.