CVE-2026-0606VulnerabilityPublished 5 Jan 2026Updated 23 Feb 2026

CVE-2026-0606: 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

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% 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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
code-projectsOnline Music Site	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2026-0606, organizations should immediately audit and sanitize all user inputs, particularly the 'ID' parameter in /FrontEnd/Albums.php, using strict whitelisting and input validation techniques. Implement parameterized queries or prepared statements to prevent SQL injection. If an official patch becomes available, apply it promptly. In the absence of patches, deploy web application firewalls (WAFs) with SQL injection detection and blocking capabilities to provide an additional layer of defense. Conduct thorough code reviews and security testing on all web-facing components. Limit database user privileges to the minimum necessary to reduce potential damage from exploitation. Monitor logs for suspicious query patterns or injection attempts. Additionally, consider isolating the vulnerable application within segmented network zones to contain potential breaches. Regularly update and maintain the software stack to reduce exposure to known vulnerabilities.

Description

A vulnerability was detected in code-projects Online Music Site 1.0. Affected by this issue is some unknown functionality of the file /FrontEnd/Albums.php. Performing a manipulation of the argument ID results in sql injection. It is possible to initiate the attack remotely. The exploit is now public and may be used.

Impact

The SQL injection vulnerability in the Online Music Site can lead to unauthorized access to sensitive data stored in the backend database, including user information, music metadata, or other confidential records. Attackers could manipulate database queries to extract data, alter records, or disrupt service availability, potentially damaging the integrity and availability of the application. For organizations, this could result in data breaches, loss of customer trust, regulatory penalties, and operational disruptions. Since the exploit requires no authentication and can be performed remotely, the attack surface is broad, especially for publicly accessible instances. The medium severity rating reflects a moderate risk, but the presence of public exploit code could increase exploitation likelihood. Organizations relying on this software or similar vulnerable web applications face increased risk of targeted attacks, data leakage, and reputational harm.

Summary

CVE-2026-0606 is a SQL injection vulnerability identified in the Online Music Site version 1.0 developed by code-projects. The vulnerability resides in the /FrontEnd/Albums.php file, where the 'ID' parameter is improperly sanitized, allowing an attacker to inject malicious SQL queries remotely without requiring authentication or user interaction. This injection flaw can be exploited to manipulate backend database queries, potentially leading to unauthorized data disclosure, modification, or deletion. The vulnerability has a CVSS 4.0 base score of 6.9, indicating a medium severity level. The attack vector is network-based with low attack complexity and no privileges or user interaction needed. The impact on confidentiality, integrity, and availability is limited but present, as the attacker can partially compromise the database. Although no known exploits are currently active in the wild, the public availability of exploit code increases the risk of exploitation. The vulnerability affects only version 1.0 of the product, and no official patches have been linked yet. The issue highlights the importance of proper input validation and parameterized queries in web applications to prevent SQL injection attacks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 23:17 UTC

Technical details

References

Community reviews

Related threats