dbcve.org
Online Music SiteApplication · Fabian

CVE-2026-0568

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-02
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 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.

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 · moderate confidence

SQL injection vulnerability in Online Music Site 1.0's /Frontend/ViewSongs.php file. The ID parameter passed to an unspecified function is not properly sanitized or parameterized, allowing an attacker to inject malicious SQL queries. This remote, critical (CVSS 9.8) flaw allows complete database compromise.

MitigationReplace dynamic SQL queries in ViewSongs.php with prepared statements/parameterized queries, implement input validation on all user-supplied parameters, and apply principle of least privilege to the database account.

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 Online Music Site installation
    Locate the application web root directory and identify if the Online Music Site (Fabian) application is present. Look for typical web application files such as index.php, configuration files, or the /Frontend/ directory structure.
    Affected if The Fabian Online Music Site application is installed on the system.
  2. Identify the software version
    Check for version information in the application. Look in README files, version configuration files, or the main index.php for a version marker. The affected version is 1.0.
    Affected if The installed version is exactly 1.0.
  3. Locate the vulnerable file
    Navigate to the /Frontend/ directory in the web root and verify that ViewSongs.php exists. The path should be [webroot]/Frontend/ViewSongs.php.
    Affected if The file /Frontend/ViewSongs.php exists in the application.
  4. Inspect the vulnerable code
    Open ViewSongs.php and examine how the ID parameter is handled. Search for $_GET['ID'] or $_POST['ID'] usage within SQL query strings without prepare() or parameter binding.
    Affected if The ID parameter is directly interpolated into SQL queries without sanitization or prepared statements.
  5. Verify web access to the vulnerable endpoint
    Attempt to access the ViewSongs.php file via HTTP request with a test ID parameter, such as: http://[host]/Frontend/ViewSongs.php?ID=1
    Affected if The endpoint is accessible over the network and accepts the ID parameter.

A system is affected if Fabian Online Music Site version 1.0 is installed, the file /Frontend/ViewSongs.php exists, and the ID parameter is used in unsanitized SQL queries within that file.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries in ViewSongs.php with prepared statements/parameterized queries, implement input validation on all user-supplied parameters, and apply principle of least privilege to the database account.

Recommended fix Moderate confidence
  1. Locate the vulnerable file /Frontend/ViewSongs.php and identify the SQL query that uses the ID parameter without proper sanitization
  2. Replace direct string concatenation of the ID parameter with prepared statements (parameterized queries)
  3. If using PDO: Use $pdo->prepare('SELECT ... WHERE id = ?') followed by $stmt->execute([$id])
  4. If using MySQLi: Use $stmt = $mysqli->prepare('SELECT ... WHERE id = ?') followed by $stmt->bind_param('i', $id)
  5. Validate and sanitize the ID input as an additional layer of defense (ensure it is a valid integer)
  6. Test the fix by attempting to inject SQL meta-characters in the ID parameter to confirm the vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Online Music Site Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0568 — 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-0568 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