CVE-2025-6306
BaseFortify
Publication date: 2025-06-20
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 |
|---|---|---|
| code-projects | online_shoe_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-6306 is a critical SQL injection vulnerability in the Online Shoe Store version 1.0, specifically in the /admin/admin_index.php file. It occurs because the 'username' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can be exploited remotely without authentication, enabling attackers to access, modify, or delete database information unauthorizedly. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, modification, or deletion of sensitive information, and potentially full system compromise. It can disrupt service availability and compromise the confidentiality, integrity, and availability of the system. Since it requires no authentication and has publicly available exploits, it poses a severe threat to system security and business continuity. [1, 2, 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 'username' parameter in the /admin/admin_index.php file for SQL injection flaws. You can use SQL injection testing tools such as sqlmap to automate detection. Example commands include using sqlmap with the POST parameter 'username' to test for injection, e.g.: sqlmap -u "http://target/admin/admin_index.php" --data="username=admin" --risk=3 --level=5. Additionally, manual testing with payloads such as boolean-based blind, error-based, and time-based blind SQL injection strings can be used to confirm the vulnerability. Example payloads include: username=admin' AND 6111=6111 AND 'GUNt'='GUNt (boolean-based), username=admin' AND (SELECT 5335 FROM(SELECT COUNT(*),CONCAT(0x7170766271,(SELECT (ELT(5335=5335,1))),0x7171707171,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a) AND 'Nlls'='Nlls (error-based), and username=admin' AND (SELECT 9767 FROM (SELECT(SLEEP(5)))iTUF) AND 'TAwD'='TAwD (time-based). [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 to ensure inputs conform to expected formats. 4) Minimizing database user permissions by avoiding use of high-privilege accounts for routine operations. 5) Conducting regular security audits to detect and fix vulnerabilities promptly. These steps help prevent exploitation and protect system integrity and confidentiality. [2, 3]