dbcve.org
Online Music SiteApplication · Fabian

CVE-2026-0569

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 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.

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

A SQL injection vulnerability exists in the /Frontend/AlbumByCategory.php file of Online Music Site 1.0. The vulnerability is caused by unsanitized user input being passed through the ID parameter, allowing remote attackers to inject arbitrary SQL commands into the database. This critical (CVSS 9.8) flaw can lead to complete database compromise, including data exfiltration, modification, or deletion.

MitigationImplement parameterized queries (prepared statements) for all database operations involving the ID parameter, combined with proper input validation. Apply the principle of least privilege to database accounts to limit the impact of any successful injection.

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 1.0 is installed
    Search for files or directories indicating this application, such as checking for the presence of the /Frontend/ directory or common installation paths. Look for identifying files like index.php, readme.txt, or license files that reference 'Online Music Site' or 'Fabian'.
    Affected if The application Fabian Online Music Site version 1.0 is present on the server.
  2. Locate the vulnerable AlbumByCategory.php file
    Search for the file /Frontend/AlbumByCategory.php within the web root directory. This file should exist within the application installation.
    Affected if The file /Frontend/AlbumByCategory.php exists in the web application directory.
  3. Check if the application is accessible over the network
    Attempt to access the file via HTTP/HTTPS request to the web server, such as visiting http://[target]/Frontend/AlbumByCategory.php or checking if the web server is serving this application.
    Affected if The vulnerable PHP file is accessible via the web server.
  4. Inspect the ID parameter handling in AlbumByCategory.php
    Open the AlbumByCategory.php file and examine how the ID parameter is processed. Look for direct use of $_GET['ID'] or $_REQUEST['ID'] in SQL queries without using prepared statements, parameter binding, or input sanitization functions like mysqli_real_escape_string or htmlspecialchars.
    Affected if The code contains SQL queries that directly incorporate the ID parameter without parameterized queries or proper escaping.

A user is affected if Fabian Online Music Site 1.0 is installed, the /Frontend/AlbumByCategory.php file is present and accessible, and the ID parameter is used directly in SQL queries without prepared statements or input sanitization.

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

Implement parameterized queries (prepared statements) for all database operations involving the ID parameter, combined with proper input validation. Apply the principle of least privilege to database accounts to limit the impact of any successful injection.

Fix this in Online Music Site Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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