CVE-2025-6160
BaseFortify
Publication date: 2025-06-17
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 |
|---|---|---|
| sourcecodester | downloading_client_database_management_system | 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-6160 is a critical SQL injection vulnerability in SourceCodester Client Database Management System version 1.0, specifically in the file /user_customer_create_order.php. It occurs because the user_id parameter is not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without authentication, potentially leading to unauthorized database access, data leakage, data tampering, full system control, and service disruption. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by compromising the confidentiality, integrity, and availability of your system. An attacker can remotely exploit the SQL injection flaw to access sensitive data, modify or delete data, gain full control over the system, and disrupt services. Since no authentication is required, the attack is straightforward and can be performed remotely, increasing the risk of exploitation. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for HTTP requests targeting the /user_customer_create_order.php file with suspicious or malicious payloads in the user_id parameter indicative of SQL injection attempts. One can use network traffic inspection tools or web server logs to identify such requests. Additionally, Google dorking with the query "inurl:user_customer_create_order.php" can help identify vulnerable targets. For active testing, sending crafted POST requests injecting SQL payloads into the user_id parameter can confirm the presence of the vulnerability. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input; 2) Applying strict input validation and filtering on the user_id parameter to ensure only expected formats are accepted; 3) Minimizing database user permissions to avoid using high-privilege accounts for routine operations; 4) Conducting regular security audits to detect and fix vulnerabilities promptly. If possible, replacing the affected component with an alternative product is also suggested. [1, 2]