CVE-2026-11490
Received Received - Intake
SQL Injection in Online Music Site 1.0

Publication date: 2026-06-08

Last updated on: 2026-06-08

Assigner: VulDB

Description
A vulnerability was determined in code-projects Online Music Site 1.0. This issue affects some unknown processing of the file /Frontend/Search.php. This manipulation of the argument Category causes sql injection. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-08
Last Modified
2026-06-08
Generated
2026-06-08
AI Q&A
2026-06-08
EPSS Evaluated
N/A
NVD
CVE-2026-11490
EUVD
EUVD-2026-35021
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
code-projects online_music_site 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions
Instant insights powered by AI
Compliance Impact

This SQL injection vulnerability allows attackers to access unauthorized data, potentially leading to data leakage and tampering.

Such unauthorized access and data compromise can violate data protection requirements under common standards and regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive information.

Therefore, exploitation of this vulnerability could result in non-compliance with these regulations due to failure to adequately protect data confidentiality and integrity.

Executive Summary

This vulnerability is a SQL injection issue found in the Online Music Site 1.0 project, specifically in the Search.php file. It occurs because the 'category' parameter is not properly sanitized or validated before being used in SQL queries.

Attackers can exploit this vulnerability by injecting malicious SQL code through the 'category' parameter, which allows them to manipulate database queries remotely without needing any login or authorization.

This can lead to unauthorized access to data, data tampering, and potentially full control over the system.

Impact Analysis

Exploiting this vulnerability can result in several serious impacts:

  • Unauthorized access to sensitive data stored in the database.
  • Data tampering or modification, which can compromise data integrity.
  • Disruption of service, such as delays caused by time-based blind SQL injection attacks.
  • Potential full control over the affected system by attackers.
Detection Guidance

This vulnerability can be detected by testing the "category" parameter in the /Frontend/Search.php file for SQL injection. A common method is to inject SQL payloads and observe the response for anomalies such as delays or error messages.

  • Use a time-based blind SQL injection test by sending a payload that causes a delay, for example, appending a payload that induces a 5-second delay to the "category" parameter.
  • Example command using curl to test for time-based SQL injection:
  • curl "http://target/Frontend/Search.php?category=1' AND IF(SLEEP(5),1,0)-- "

If the response is delayed by approximately 5 seconds, it indicates the presence of the SQL injection vulnerability.

Mitigation Strategies

Immediate mitigation steps include:

  • Implement prepared statements (parameterized queries) to safely handle the "category" parameter and prevent SQL injection.
  • Validate and filter all user inputs, especially the "category" parameter, to ensure only expected values are processed.
  • Minimize database user permissions to limit the impact of a potential SQL injection attack.
  • If possible, apply patches or updates provided by the software vendor addressing this vulnerability.
Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-11490. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart