CVE-2025-15408
BaseFortify
Publication date: 2026-01-01
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 |
|---|---|---|
| anisha | online_guitar_store | 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?
CVE-2025-15408 is a SQL injection vulnerability in the Online Guitar Store version 1.0, specifically in the /admin/Create_product.php file. The vulnerability occurs because the 'dre_title' parameter is used directly in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code. This flaw enables remote attackers to manipulate SQL queries, potentially compromising the database and the application without requiring authentication. [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. Attackers can exploit it remotely without authentication, which makes it easier to carry out attacks that compromise confidentiality, integrity, and availability of the affected system. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'dre_title' parameter in the /admin/Create_product.php endpoint for SQL injection. A common approach is to use automated tools like sqlmap to perform time-based blind SQL injection tests. For example, you can run a command such as: sqlmap -u "http://targetsite/admin/Create_product.php" --data="dre_title=TEST" --method=POST --technique=T --level=5 --risk=3 to test the POST parameter 'dre_title'. Additionally, attackers may be located using Google dorking with the query: inurl:admin/Create_product.php to find vulnerable targets. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Enforce strict input validation and filtering on the 'dre_title' parameter to ensure inputs conform to expected formats and block malicious data. 3) Minimize database user privileges by avoiding the use of high-privilege accounts for routine database operations. 4) Consider replacing the affected software with an alternative product, as no known mitigations or countermeasures have been identified. These steps collectively reduce the risk of SQL injection and improve security. [1, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows remote attackers to perform SQL injection, potentially leading to unauthorized access, data leakage, and data tampering. Such compromises of confidentiality, integrity, and availability of data can negatively impact compliance with standards and regulations like GDPR and HIPAA, which require protection of sensitive data and maintaining data integrity. However, no explicit mention of compliance impact is provided in the resources. [1, 2]