Skip to main content
CVE-2026-0568VulnerabilityPublished Updated

CVE-2026-0568: code-projects Online Music Site · SQL Injection

Affects code-projects Online Music SiteSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 32% 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:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
code-projectsOnline Music SiteAffected
  • =1.0
Fixed in–
GitHublimingqian123/CVEpkg:github/limingqian123/CVEOther threatsAffected
  • =1.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-0568, organizations should immediately audit the /Frontend/ViewSongs.php file and any related code handling the 'ID' parameter. Specific recommendations include: 1) Implement strict input validation and sanitization to ensure the 'ID' parameter only accepts expected numeric or alphanumeric values. 2) Use parameterized queries or prepared statements to prevent direct concatenation of user input into SQL commands. 3) Employ web application firewalls (WAFs) with rules targeting SQL injection patterns to provide an additional layer of defense. 4) Monitor logs for suspicious query patterns or repeated access attempts to the vulnerable endpoint. 5) If possible, isolate the database with least privilege access controls to limit the impact of a successful injection. 6) Engage with the vendor or community to obtain or develop patches or updated versions that address this vulnerability. 7) Conduct penetration testing and code reviews to identify and remediate similar injection flaws elsewhere in the application. 8) Educate developers on secure coding practices to prevent recurrence.

Description

A flaw has been found in code-projects Online Music Site 1.0. The impacted element is an unknown function of the file /Frontend/ViewSongs.php. This manipulation of the argument ID causes sql injection. It is possible to initiate the attack remotely. The exploit has been published and may be used.

References

Community reviews

Loading reviews…