CVE-2026-0570
SQL Injection in Online Music Site 1.0 Feedback.php Allows Remote Exploit
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-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-0570 is a SQL injection vulnerability in the Online Music Site version 1.0, specifically in the Feedback.php file. The vulnerability occurs because the 'fname' 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 actions such as data access, modification, or disruption. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, data tampering, full system compromise, and service disruption. Attackers can execute arbitrary SQL commands without authentication, potentially gaining control over the system and compromising confidentiality, integrity, and availability of data and services. [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 'fname' parameter in POST requests to /Frontend/Feedback.php for SQL injection. Tools like sqlmap can be used to automate detection with payloads targeting boolean-based blind, error-based, and time-based blind SQL injection techniques. An example test command using sqlmap would be: sqlmap -u "http://target/mis/Frontend/Feedback.php" --data="fname=222&other=params" --risk=3 --level=5 --technique=BEUST --dbms=MySQL. Additionally, attackers can be identified by searching for URLs containing 'inurl:Frontend/Feedback.php' using Google dorking to find vulnerable endpoints. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Implement strict input validation and filtering on the 'fname' parameter to ensure it conforms to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding high-privilege accounts like 'root' or 'admin' for routine operations. 4) Consider replacing the affected component with an alternative product if possible. These steps help protect system security and maintain data integrity. [2, 3, 1]