CVE-2025-14246
BaseFortify
Publication date: 2025-12-08
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 | simple_shopping_cart | 1.0 |
| fabian | simple_shopping_cart | 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-14246 is a critical SQL injection vulnerability in version 1.0 of the Simple Shopping Cart software, specifically in the file /Customers/settings.php. It occurs because the user_id parameter is improperly handled and directly used in SQL queries without proper validation or sanitization. This allows attackers to inject malicious SQL code remotely, potentially accessing, modifying, or deleting database information without authentication. The vulnerability can be exploited via a multipart POST request manipulating the user_id input. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to the database, data leakage, modification or deletion of data, full system compromise, and potential service disruption. Since it can be exploited remotely without authentication, attackers can manipulate the database to harm confidentiality, integrity, and availability of the system. This could result in loss of sensitive information and operational downtime. [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 'user_id' parameter in the /Customers/settings.php file for SQL injection using specially crafted payloads. A proof-of-concept involves sending a multipart POST request with a payload such as: Content-Disposition: form-data; name="user_id" 4' AND (SELECT 5683 FROM (SELECT(SLEEP(5)))kgfD) AND 'bvYa'='bvYa. Tools like sqlmap can be used to automate detection and enumeration of the vulnerability by targeting this parameter. Additionally, attackers may be identified by monitoring for unusual multipart POST requests with suspicious 'user_id' values. Google dorking with the query inurl:Customers/settings.php can help identify vulnerable targets externally. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Applying strict input validation and filtering to ensure 'user_id' inputs conform to expected formats. 3) Minimizing database user permissions by avoiding use of high-privilege accounts for routine operations. 4) Conducting regular security audits of code and systems to detect and fix vulnerabilities promptly. If possible, replacing the affected software with an alternative product is also suggested. [1, 2, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized database access, data leakage, and modification, which can lead to exposure of sensitive personal or protected health information. Such data breaches can result in non-compliance with standards and regulations like GDPR and HIPAA that require protection of confidential data and maintaining data integrity and confidentiality. Therefore, exploitation of this vulnerability could negatively impact compliance with these regulations by compromising data security and privacy. [1, 3]