dbcve.org
Online Music SiteApplication · Fabian

CVE-2026-2212

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-09
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 was identified in code-projects Online Music Site 1.0. Affected by this vulnerability is an unknown functionality of the file /Administrator/PHP/AdminEditCategory.php. The manipulation of the argument ID leads to sql injection. The attack is possible to be carried out remotely. The exploit is publicly available and might 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 code-projects Online Music Site 1.0 allows remote attackers to manipulate the ID parameter in /Administrator/PHP/AdminEditCategory.php to inject arbitrary SQL commands, potentially leading to unauthorized database access, data exfiltration, or complete system compromise.

MitigationImplement prepared statements/parameterized queries for all database operations in AdminEditCategory.php, specifically sanitizing the ID parameter before using it in SQL queries. Conduct a full audit of similar files for additional SQL injection vulnerabilities.

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 code-projects Online Music Site in your web server's document root. Search for the /Administrator/PHP/AdminEditCategory.php file path.
    Affected if The application is installed and AdminEditCategory.php exists on the server
  2. Identify the application version
    Examine version files, README files, or header comments in the main PHP files of the application to determine the installed version.
    Affected if The installed version is Fabian Online Music Site 1.0
  3. Inspect the vulnerable file for SQL injection patterns
    Open /Administrator/PHP/AdminEditCategory.php and review how the ID parameter is handled in SQL queries. Look for direct string concatenation or unsanitized variable insertion into SQL statements.
    Affected if The ID parameter is used directly in SQL queries without prepared statements, parameter binding, or input sanitization
  4. Verify remote accessibility
    Check if the /Administrator/PHP/AdminEditCategory.php endpoint is accessible from the network. Confirm the application is exposed to remote requests.
    Affected if The vulnerable endpoint is reachable remotely without authentication restrictions

A user is affected if they have Fabian Online Music Site version 1.0 installed with the AdminEditCategory.php file accessible and the ID parameter used unsafely in SQL queries.

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

Implement prepared statements/parameterized queries for all database operations in AdminEditCategory.php, specifically sanitizing the ID parameter before using it in SQL queries. Conduct a full audit of similar files for additional SQL injection vulnerabilities.

Recommended fix Moderate confidence
  1. Replace dynamic SQL queries in /Administrator/PHP/AdminEditCategory.php with prepared statements (PDO or MySQLi). For example, change `$db->query("SELECT * FROM categories WHERE ID = " . $_GET['ID'])` to a parameterized query like `$stmt = $pdo->prepare('SELECT * FROM categories WHERE ID = :id'); $stmt->execute([':id' => $_GET['ID']]);`
  2. Validate and sanitize the ID parameter using type casting (e.g., (int)$_GET['ID']) or integer validation before using it in any query
  3. Apply principle of least privilege: ensure the database user connecting from the application has only necessary permissions (SELECT, UPDATE, INSERT where needed, but not DROP or administrative privileges)
  4. Implement output encoding when displaying any data retrieved from the database to prevent secondary XSS issues
  5. Restrict access to /Administrator/ directory using HTTP authentication or IP allow-listing if not already protected
  6. Audit all other PHP files in the application for similar SQL injection vulnerabilities and apply the same parameterized query pattern
Caveat No official upgrade path available; this is a third-party educational project without maintained security releases

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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