CVE-2026-0570: code-projects Online Music Site · SQL Injection
Affects code-projects Online Music SiteSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 2 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| code-projectsOnline Music Site | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2026-0570, organizations should implement the following specific measures: 1) Immediately review and sanitize all user inputs, especially the 'fname' parameter in /Frontend/Feedback.php, using strict whitelisting and input validation techniques. 2) Refactor the vulnerable code to use parameterized queries or prepared statements to prevent SQL injection. 3) Restrict database user permissions to the minimum necessary, avoiding use of high-privilege accounts for web application database connections. 4) Monitor web application logs for suspicious input patterns targeting the 'fname' parameter or feedback functionality. 5) If possible, apply any vendor patches or updates once released; if no patches are available, consider temporary workarounds such as web application firewalls (WAFs) configured to block SQL injection attempts targeting this endpoint. 6) Conduct a thorough security review of the entire application to identify and remediate similar injection flaws. 7) Educate developers on secure coding practices to prevent recurrence. 8) Isolate the affected application environment to limit lateral movement in case of compromise.
Description
A vulnerability was found in code-projects Online Music Site 1.0. This impacts an unknown function of the file /Frontend/Feedback.php. Performing a manipulation of the argument fname results in sql injection. The attack can be initiated remotely. The exploit has been made public and could be used.