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

CVE-2026-0607: 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 38% 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-0607, organizations should immediately implement the following specific measures: 1) Apply strict input validation and sanitization on the ID parameter in /Administrator/PHP/AdminViewSongs.php to reject or properly escape malicious SQL syntax. 2) Refactor the code to use parameterized queries or prepared statements to prevent SQL Injection. 3) Restrict access to the administration interface by IP whitelisting, VPN, or multi-factor authentication to reduce exposure. 4) Monitor database logs and web server logs for unusual query patterns or injection attempts targeting the ID parameter. 5) If patch updates become available from the vendor, prioritize their deployment. 6) Conduct a security audit of the entire application to identify and remediate other injection points or vulnerabilities. 7) Educate developers on secure coding practices to prevent similar issues in future releases. 8) Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block SQL Injection payloads targeting this endpoint. These targeted actions go beyond generic advice and address the specific attack vector and context of this vulnerability.

Description

A flaw has been found in code-projects Online Music Site 1.0. This affects an unknown part of the file /Administrator/PHP/AdminViewSongs.php. Executing a manipulation of the argument ID can lead to sql injection. It is possible to launch the attack remotely. The exploit has been published and may be used.

Impact

The impact of CVE-2026-0607 on organizations using the affected Online Music Site 1.0 software can be significant. Successful exploitation allows attackers to remotely execute arbitrary SQL commands on the backend database without authentication, potentially leading to unauthorized access to sensitive data such as user information, song metadata, or administrative credentials. Attackers could also modify or delete data, disrupting service availability or corrupting the database. This could result in data breaches, loss of customer trust, regulatory penalties, and operational downtime. Since the administration interface is targeted, attackers might gain elevated privileges or pivot to other parts of the network. The medium severity rating reflects that while the vulnerability is serious, the scope of affected systems is limited to users of this specific software version. However, the public availability of exploit code increases the likelihood of exploitation attempts, especially by opportunistic attackers. Organizations relying on this software for music content management or streaming services face reputational and financial risks if the vulnerability is exploited.

Summary

CVE-2026-0607 identifies a SQL Injection vulnerability in the Online Music Site software developed by code-projects, specifically version 1.0. The vulnerability resides in the /Administrator/PHP/AdminViewSongs.php file, where the ID parameter is improperly sanitized, allowing an attacker to inject malicious SQL code. This injection can be performed remotely without requiring authentication or user interaction, making it easier to exploit. The flaw enables attackers to manipulate backend database queries, potentially leading to unauthorized data disclosure, modification, or deletion. The vulnerability affects the confidentiality, integrity, and availability of the database, though the impact is considered limited (low) in scope per the CVSS vector. The CVSS 4.0 score is 6.9 (medium severity), reflecting the ease of remote exploitation and the potential consequences. While no known exploits are actively observed in the wild, the availability of exploit code increases the risk of future attacks. The lack of patches or official fixes at the time of publication necessitates immediate mitigation efforts by users of this software. This vulnerability highlights the critical need for secure coding practices such as input validation and the use of parameterized queries 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