CVE-2025-6317
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-6317 is a critical SQL injection vulnerability in version 1.0 of the Online Shoe Store project, specifically in the /admin/confirm.php file. The vulnerability occurs because the 'id' parameter from HTTP GET requests is used directly in SQL queries without proper input validation or sanitization. This allows attackers to inject malicious SQL code remotely without authentication, potentially leading to unauthorized database access, data leakage, data tampering, and full system control. [1, 2]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive data, modification or tampering of data, disruption of services, and potentially full control over the affected system. Since exploitation does not require authentication and can be performed remotely, attackers can easily compromise the system, leading to loss of confidentiality, integrity, and availability. [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 vulnerable URL parameter 'id' in /admin/confirm.php for SQL injection. Commands using sqlmap can be employed, for example: sqlmap -u "http://<target>/online-shoe/admin/confirm.php?id=1" --batch --dbs. Additionally, manual testing with payloads such as id=1' RLIKE (SELECT (CASE WHEN (2850=2850) THEN 1 ELSE 0x28 END))-- or id=1' AND (SELECT SLEEP(5))-- can help identify boolean-based or time-based blind SQL injection. Network detection can also involve searching for HTTP GET requests with suspicious SQL injection patterns targeting the 'id' parameter. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to prevent SQL injection. 2) Apply strict input validation and filtering on the 'id' parameter to ensure only expected input formats are accepted. 3) Minimize database user privileges by avoiding use of high-privilege accounts for the application database connection. 4) Conduct regular security audits and code reviews to detect and fix vulnerabilities promptly. If possible, replace the affected component with a secure alternative. [1, 2]