Safeguard
Vulnerability Analysis•

CVE-2026-2212: SQL Injection in Online Music Site

CVE-2026-2212 is a High SQL injection flaw in Online Music Site 1.0 with no listed fix. Keep it off public networks and use prepared statements.

Safeguard Security Team
3 min read

CVE-2026-2212 is a SQL injection flaw in code-projects Online Music Site 1.0, scored 7.3 (High) in the CVE record. The weak spot is the ID parameter of the edit category page. The record lists no fixed version, so take the app off public networks, and if you maintain the code, replace string built queries with prepared statements.

What's affected

  • Product: code-projects Online Music Site
  • Affected version: 1.0
  • Location: /Administrator/PHP/AdminEditCategory.php (Admin edit category page)
  • Input at issue: the ID parameter of the edit category page
  • Fixed version: none listed in the record

The record says the exploit has been disclosed publicly. It does not say the flaw is being used in attacks, and the CVE is not in the CISA Known Exploited Vulnerabilities catalog.

Check the project page or vendor site for a newer release.

How to check if you're exposed

Inventory comes first. Small PHP apps get copied to shared hosts and test machines, and nobody writes them down.

find /var/www /srv /opt /home -path "*/Administrator/PHP/AdminEditCategory.php" 2>/dev/null

If the file turns up, confirm the app is version 1.0 and whether the web server answers from outside your network. Then open that file and read how it builds its database query. If the request value is joined into the SQL text instead of passed as a bound parameter, the weakness is present.

What to do now

  1. Find every copy of the app, including staging and backup hosts.
  2. If it faces the internet, take it offline or put it behind a VPN or an allow list of known addresses now.
  3. Check the project page for a patched release. If none exists, plan to retire the app or fix the query yourself.
  4. If you keep it, change the affected query to use prepared statements with bound parameters, and give the database account only the rights the app needs.
  5. Review web server and database logs for odd requests to the affected page.

Why it matters

This is the old and well understood weakness CWE-89, listed alongside CWE-74. Input reaches the database without being kept apart from the command, and the CVSS vector reflects a remote attack that needs no privileges and no user action.

With no fixed release listed, the dependable controls are network limits, a query fix and monitoring. None of them need a vendor.

Quick check

Is there a patch for this?

The record lists no fixed version. Check the project page or vendor site, and until you find one, limit network access to the app.

Does a dependency scan find this?

Not by itself. Dependency tools match known library versions. This weakness lives in the application source, so look at the query code directly.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.