CVE-2025-15407
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-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-2025-15407 is a SQL injection vulnerability in version 1.0 of the Online Guitar Store, specifically in the /admin/Create_category.php file. The vulnerability occurs because the parameter dre_Ctitle is used directly in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code remotely without authentication. This can lead to unauthorized database access and manipulation. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute arbitrary SQL commands remotely, leading to unauthorized access to sensitive data, modification or deletion of data, full system control, and disruption of services. It impacts the 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 parameter 'dre_Ctitle' in the /admin/Create_category.php file for SQL injection. One method is to use sqlmap with a payload targeting the POST parameter 'dre_Ctitle', for example: sqlmap -u "http://target/admin/Create_category.php" --data="dre_Ctitle=optics" --technique=T --dbms=MySQL. Additionally, Google dorking can help identify vulnerable targets by searching for 'inurl:admin/Create_category.php'. The vulnerability is a time-based blind SQL injection, so payloads causing delays (e.g., using SLEEP(5)) can confirm the issue. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected component or upgrading to a non-vulnerable version if available. 2) Implementing prepared statements with parameter binding to separate SQL code from user input. 3) Applying strict input validation and filtering on the 'dre_Ctitle' parameter to ensure it conforms to expected formats. 4) Limiting database user permissions to the minimum necessary, avoiding high-privilege accounts like 'root' or 'admin' for routine operations. These steps help prevent exploitation and protect system security and data integrity. [2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows remote attackers to execute arbitrary SQL commands, potentially leading to unauthorized access, data leakage, modification, or deletion of sensitive information. Such impacts on confidentiality, integrity, and availability of data can result in non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive data. Immediate remediation is critical to maintain data security and compliance. [1, 2, 3]