CVE-2026-1533
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 · uneditedA security flaw has been discovered in code-projects Online Music Site 1.0. The impacted element is an unknown function of the file /Administrator/PHP/AdminAddCategory.php. The manipulation results in sql injection. The attack may be performed from remote. The exploit has been released to the public and may be used for attacks.
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 confidenceA critical SQL injection vulnerability exists in the AdminAddCategory.php file of the code-projects Online Music Site 1.0. The vulnerability allows unauthenticated remote attackers to inject malicious SQL queries through an unknown function in the administrator interface, potentially enabling complete database compromise.
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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Online Music Site is installedSearch the web server document root for files or directories containing 'music', 'online music site', or 'fabian' in the name. Check for the presence of AdminAddCategory.php file.Affected if The application 'Fabian Online Music Site' or 'code-projects Online Music Site' version 1.0 is found on the server.
-
Verify the installed versionCheck any version files, README files, or the site footer/admin panel for a version number. Compare against the affected version 1.0.Affected if The installed version is exactly 1.0.
-
Locate AdminAddCategory.phpFind AdminAddCategory.php in the web application directory, typically under /admin, /administrator, or the main application root.Affected if The file AdminAddCategory.php exists in the application directory.
-
Check admin interface exposureAttempt to access the administrator login page and the AdminAddCategory.php file directly via HTTP/HTTPS from an unauthenticated perspective. Check if the /admin or /administrator route is publicly accessible.Affected if The administrator interface or AdminAddCategory.php is reachable without authentication.
-
Inspect SQL query handling in AdminAddCategory.phpOpen AdminAddCategory.php and examine database query code. Look for direct string concatenation in SQL statements (e.g., 'SELECT * FROM ... ' . $variable) rather than prepared statements or parameterized queries.Affected if The code uses direct variable interpolation or concatenation in SQL queries without input sanitization or prepared statements.
You are affected if you have Fabian Online Music Site version 1.0 installed with the vulnerable AdminAddCategory.php file present and the admin interface accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement parameterized queries (prepared statements) for all database operations in AdminAddCategory.php and apply proper input validation and sanitization. Additionally, apply the principle of least privilege to database accounts and consider web application firewall deployment as a defensive layer.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1533 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1533 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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