CVE-2026-0568
SQL Injection in Online Music Site 1.0 /Frontend/ViewSongs.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-0568 is a SQL injection vulnerability in code-projects Online Music Site version 1.0, specifically in the file /Frontend/ViewSongs.php. The vulnerability occurs because the 'id' parameter is not properly sanitized or validated before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without authentication, potentially manipulating the database by extracting, modifying, or deleting data. The flaw corresponds to CWE-89 (Improper Neutralization of Special Elements used in an SQL Command). [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to gain unauthorized access to your database, leak sensitive information, modify or tamper with data, gain full system control, and disrupt services. Since it can be exploited remotely without authentication, it poses a high risk to the confidentiality, integrity, and availability of your system. Attackers can use various SQL injection techniques such as boolean-based blind, error-based, time-based blind, and UNION-based injections to exploit this flaw. [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 'id' parameter in HTTP GET requests to the /Frontend/ViewSongs.php file for SQL injection. One suggested command is using sqlmap, an automated SQL injection tool, with the following example: sqlmap -u "http://localhost/mis/Frontend/ViewSongs.php?id=109" -p id --dbs --batch. Additionally, attackers can identify vulnerable targets using Google dorking with the query: inurl:Frontend/ViewSongs.php. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements and parameter binding to separate SQL code from user input, preventing SQL injection. 2) Implement strict input validation and filtering on the 'id' parameter to ensure only expected formats are accepted. 3) Apply the principle of least privilege by configuring the database user with minimal permissions, avoiding high-privilege accounts for routine operations. Since no known countermeasures or patches are available, replacing the affected component with an alternative product is also suggested. [1, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows attackers to perform SQL injection attacks that can compromise the confidentiality, integrity, and availability of the affected system. This can lead to unauthorized access, data leakage, data modification, and service disruption. Such impacts can result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive data against unauthorized access and ensuring data integrity and availability. Therefore, this vulnerability poses a significant risk to compliance with these common standards and regulations. [1, 3]