CVE-2026-0606 is a SQL injection flaw in Online Music Site 1.0 from code-projects, in /FrontEnd/Albums.php. NVD scores it 7.3, high severity, and the record says an exploit has been published. No fixed version is listed, so the fix is to correct the query in your copy or take the app offline.
What's affected
- Product: Online Music Site, version 1.0, from code-projects.
- Component: /FrontEnd/Albums.php, parameter ID.
- Fixed version: none listed in the CVE record or the public report. Check the vendor page for any newer release.
- Severity: CVSS 7.3, vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L. The vector lists no privileges required. - Exploitation: the record says exploit details are public. It is not on the CISA Known Exploited Vulnerabilities list.
How to check if you're exposed
This is source code you host, so first find out whether you run it.
find /var/www -type f -path "*Albums.php" 2>/dev/null
If the file exists and the site is reachable from the internet, treat it as exposed. Then search your access logs for requests to Albums.php.
What to do now
- Take the app off the public internet, or put it behind a VPN or an authenticating reverse proxy, until the query is fixed.
- If you keep running it, change the code in Albums.php so ID reaches the database through a prepared statement (PDO or mysqli) instead of string concatenation.
- Run the database account for this app with only the privileges it needs. It should not own the schema or be able to read other databases.
- Search access logs for unusual requests to Albums.php and for database errors in the PHP log, then reset any passwords that may have been exposed.
Why it matters
The weakness is CWE-89 (improper neutralization of special elements in an SQL command), a child of CWE-74 (injection). The app builds a query by pasting request data straight into SQL text, so the database cannot tell data from instructions. The public report for this product family describes that exact pattern.
The album page is on the public front end, so any visitor reaches it. The CVSS vector lists no privileges required. Public catalogue pages that look up a row by ID are the most common place for this flaw, because the ID feels like a number and gets less care than a form field.
Quick check
Is there a patch for CVE-2026-0606?
None is listed in the CVE record. Check code-projects for a newer release, and if there is none, fix the query yourself or stop running the app.
Why do ID lookups so often have this flaw?
An ID looks like a number, so developers skip validation. Servers receive text regardless. Bind it as a parameter and cast it to an integer.
Sources
Last reviewed: 19 October 2026.
