CVE-2025-6305
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-6305 is a critical SQL injection vulnerability in the Online Shoe Store version 1.0, specifically in the /admin/admin_feature.php file. It occurs because the product_code parameter is improperly handled and not adequately validated or sanitized, allowing attackers to inject malicious SQL commands. This enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data modification or deletion, and potentially full system compromise. Attackers can exploit it remotely without authentication, which may result in service disruption and loss of data integrity and confidentiality, severely impacting 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 /admin/admin_feature.php endpoint for SQL injection via the product_code parameter. A proof-of-concept involves sending a multipart POST request with a payload that injects SQL commands such as a time-based blind SQL injection using SLEEP(5) to observe response delays. Additionally, Google dorking with queries like inurl:admin/admin_feature.php can help identify vulnerable targets. Specific commands include using curl or similar tools to send crafted POST requests with malicious product_code values and monitoring the response time or error messages indicative of SQL injection. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected component or upgrading to a secure version if available. 2) Implementing prepared statements with parameter binding to prevent SQL injection. 3) Applying strict input validation and filtering on the product_code parameter to ensure it conforms to expected formats. 4) Minimizing database user permissions by avoiding use of high-privilege accounts for routine database operations. 5) Conducting regular security audits to detect and remediate vulnerabilities promptly. [1, 3]