CVE-2026-0569
SQL Injection in Online Music Site 1.0 AlbumByCategory.php
Publication date: 2026-01-02
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-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-0569 is a SQL injection vulnerability in version 1.0 of the Online Music Site project, specifically in the AlbumByCategory.php file. The vulnerability occurs because the 'id' 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 and perform unauthorized database operations remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, full system compromise, and potential service disruption. Attackers can exploit it remotely without authentication, potentially compromising the confidentiality, integrity, and availability of the system. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the 'id' parameter in the URL for injection flaws. For example, you can use the sqlmap tool with the command: sqlmap -u "http://localhost/mis/Frontend/AlbumByCategory.php?id=29" -p id --dbs --batch. Additionally, manual testing can be done by injecting payloads such as '29' AND 9388=9388 AND 'JFxk'='JFxk' (boolean-based) or '29' AND (SELECT SLEEP(5)) (time-based) into the 'id' parameter to observe abnormal behavior or delays indicating vulnerability. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'id' parameter to ensure only expected input is accepted, and minimizing database user permissions by avoiding the use of high-privilege accounts for routine database operations. These measures help protect system security and maintain data integrity. [2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not explicitly discuss the impact of this SQL injection vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, since the vulnerability allows unauthorized database access, data leakage, and data tampering, it could potentially lead to non-compliance with data protection regulations that require safeguarding personal and sensitive information. Immediate remediation is necessary to maintain data integrity and system security, which are critical for compliance. [1, 2, 3]