dbcve.org
Online Music SiteApplication · Fabian

CVE-2026-0605

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A security vulnerability has been detected in code-projects Online Music Site 1.0. Affected by this vulnerability is an unknown functionality of the file /login.php. Such manipulation of the argument username/password leads to sql injection. The attack may be performed from remote. The exploit has been disclosed publicly and may be used.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in the login.php file of code-projects Online Music Site 1.0 allows remote attackers to inject malicious SQL commands through the username and/or password parameters without proper sanitization or parameterized queries.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries, implement input validation and escaping, and apply output encoding. Consider deploying a WAF as an interim protective measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Online Music SiteApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the Online Music Site version
    Locate the application files and check the version declaration in the source code, typically in a README, version file, or main configuration file
    Affected if The installed version is exactly 1.0 of Fabian Online Music Site or code-projects Online Music Site
  2. Locate the login.php file
    Search the web root directory for a file named login.php that handles authentication, typically found in the admin or user authentication module
    Affected if The login.php file exists in the application directory and is accessible via web requests
  3. Inspect the SQL query logic in login.php
    Open login.php and examine the database query code that handles the username and password parameters. Look for direct concatenation of user input into SQL statements
    Affected if The code contains SQL queries that concatenate $_POST or $_GET parameters (username/password) directly into the query string without using prepared statements or parameter binding
  4. Verify input sanitization is absent or inadequate
    Check if the username and password variables are passed through functions like mysqli_real_escape_string, htmlspecialchars, or input validation before being used in SQL queries
    Affected if No sanitization functions or parameterized queries are used, and user input flows directly into the SQL query
  5. Confirm the login functionality is accessible
    Attempt to access the login.php file via HTTP/HTTPS to verify it is reachable and actively handles user authentication
    Affected if The login.php is publicly accessible and processes user credentials through the vulnerable code path

You are affected if you have Fabian Online Music Site version 1.0 installed with the login.php file accessible and the code contains direct SQL query construction using unsanitized username/password parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with prepared statements/parameterized queries, implement input validation and escaping, and apply output encoding. Consider deploying a WAF as an interim protective measure.

Fix this in Online Music Site Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0605 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0605 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data