Skip to main content
CVE-2026-0569VulnerabilityPublished Updated

CVE-2026-0569: 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-0569, organizations should first verify if they are running code-projects Online Music Site version 1.0 and prioritize upgrading to a patched version once available. In the absence of an official patch, immediate steps include implementing strict input validation and sanitization for the 'ID' parameter in /Frontend/AlbumByCategory.php to prevent injection of malicious SQL code. Refactoring the code to use parameterized queries or prepared statements is strongly recommended to eliminate SQL injection risks. Additionally, deploying Web Application Firewalls (WAFs) with rules targeting SQL injection patterns can provide a temporary protective layer. Monitoring database logs and application behavior for unusual queries or access patterns can help detect exploitation attempts early. Restricting database user privileges to the minimum necessary can limit the damage if exploitation occurs. Finally, organizations should conduct security audits and penetration testing focused on injection vulnerabilities to identify and remediate similar issues proactively.

Description

A vulnerability has been found in code-projects Online Music Site 1.0. This affects an unknown function of the file /Frontend/AlbumByCategory.php. Such manipulation of the argument ID leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…