CVE-2026-2132
SQL Injection in Online Music Site AdminUpdateCategory.php Allows Remote Exploit
Publication date: 2026-02-08
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| fabian | online_music_site | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-2132 is a critical SQL injection vulnerability found in code-projects Online Music Site version 1.0, specifically in the file /Administrator/PHP/AdminUpdateCategory.php.'}, {'type': 'paragraph', 'content': 'The vulnerability arises because the parameter "txtcat" is directly incorporated into SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code.'}, {'type': 'paragraph', 'content': 'This flaw allows an attacker to remotely execute arbitrary SQL commands without requiring any authentication, impacting the confidentiality, integrity, and availability of the system.'}, {'type': 'paragraph', 'content': 'Multiple SQL injection techniques can be used, including Boolean-based blind, error-based, and time-based blind SQL injection, with payloads sent via multipart/form-data POST requests.'}, {'type': 'paragraph', 'content': 'Exploitation can lead to unauthorized database access, data leakage, data tampering, full system compromise, and potential service disruption.'}] [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive data, and tampering with stored information.
Attackers can manipulate SQL queries remotely without authentication, potentially leading to full system compromise and disruption of services.
The availability, integrity, and confidentiality of the affected system are at risk due to this flaw.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by testing the /Administrator/PHP/AdminUpdateCategory.php endpoint for SQL injection via the txtcat parameter.'}, {'type': 'paragraph', 'content': 'Attackers and testers can use SQL injection testing tools such as sqlmap to confirm the vulnerability by sending specially crafted multipart/form-data POST requests targeting the txtcat parameter.'}, {'type': 'list_item', 'content': 'Use sqlmap with a command like: sqlmap -u "http://target/Administrator/PHP/AdminUpdateCategory.php" --data="txtcat=TEST&id=1&txtdesc=desc&txtimage=image" --method=POST --technique=BEUSTQ'}, {'type': 'list_item', 'content': 'Search for the vulnerable endpoint on your network or externally using Google dorking with the query: inurl:Administrator/PHP/AdminUpdateCategory.php'}] [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Replace or update the vulnerable component, as no known mitigations or patches are documented.
- Implement prepared statements with parameter binding to separate SQL code from user input, preventing SQL injection.
- Enforce strict input validation and filtering on the txtcat parameter to ensure inputs conform to expected formats.
- Restrict database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations.
Taking these steps is critical to protect system security and maintain data integrity.