CVE-2026-1443
BaseFortify
Publication date: 2026-01-26
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-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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-1443 is a SQL injection vulnerability in version 1.0 of the code-projects Online Music Site, specifically in the file /Administrator/PHP/AdminDeleteUser.php. The vulnerability occurs because the 'id' parameter is directly incorporated into SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code. This flaw enables attackers to manipulate SQL commands remotely without authentication, potentially compromising the system's confidentiality, integrity, and availability. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, full system compromise, and potential service disruption. Since the attack can be executed remotely without authentication, attackers can manipulate SQL queries to delete users or perform other unauthorized operations, severely impacting system security and data integrity. [1, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'id' parameter in the /Administrator/PHP/AdminDeleteUser.php file for SQL injection. You can use tools like sqlmap to automate detection. For example, run: sqlmap -u "http://target/Administrator/PHP/AdminDeleteUser.php?id=1" --batch to test for injection. Additionally, manual testing can include sending crafted HTTP GET requests with payloads that trigger Boolean-based blind injection (using MySQL RLIKE), error-based injection (using EXTRACTVALUE), or time-based blind injection (using SLEEP). Also, Google Dorking with the query inurl:Administrator/PHP/AdminDeleteUser.php can help identify vulnerable targets. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected component with an alternative product if possible, as no known countermeasures currently exist. 2) Implementing prepared statements with parameter binding to separate SQL code from user input. 3) Applying strict input validation and filtering on the 'id' parameter to ensure it conforms to expected formats. 4) Limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts like 'root' or 'admin' for routine operations. These steps help prevent SQL injection exploitation and protect system security and data integrity. [1, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This SQL injection vulnerability impacts the confidentiality, integrity, and availability of the system, which are core principles in many compliance standards such as GDPR and HIPAA. Exploitation could lead to unauthorized access, data leakage, and data tampering, potentially resulting in violations of data protection regulations that require safeguarding personal and sensitive information. Therefore, failure to remediate this vulnerability could lead to non-compliance with these standards. [1, 3]