CVE-2025-14968
BaseFortify
Publication date: 2025-12-19
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 |
|---|---|---|
| carmelo | simple_stock_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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized remote attackers to perform SQL injection attacks, leading to unauthorized database access, data leakage, data tampering, and potential full system compromise. Such breaches of confidentiality and integrity can result in non-compliance with data protection standards and regulations like GDPR and HIPAA, which require safeguarding personal and sensitive data against unauthorized access and ensuring data integrity. Therefore, exploitation of this vulnerability could lead to violations of these compliance requirements. [1, 2]
Can you explain this vulnerability to me?
CVE-2025-14968 is a SQL injection vulnerability in version 1.0 of the Simple Stock System, specifically in the /market/update.php file. The vulnerability occurs because the 'email' parameter is not properly sanitized or validated before being used in SQL queries, allowing attackers to inject malicious SQL code. This flaw enables attackers to manipulate database queries remotely without authentication, potentially compromising the system's confidentiality, integrity, and availability. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, full system control, and potential service disruption. Attackers can exploit it remotely without authentication, which makes it easy to launch attacks that compromise the confidentiality, integrity, and availability of the affected system. [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 /market/update.php endpoint for SQL injection via the 'email' parameter. One approach is to use automated tools like sqlmap to test for SQL injection by sending crafted requests to the vulnerable parameter. For example, you can run a command such as: sqlmap -u "http://target/market/[email protected]" --batch --dbs. Additionally, searching for instances of the vulnerable endpoint using Google dorking with queries like 'inurl:market/update.php' can help identify potentially affected systems. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected software with an alternative product if possible, as no official patches are documented. 2) Implementing prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 3) Applying strict input validation and filtering on the 'email' parameter to ensure it conforms to expected formats. 4) Limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as 'root' or 'admin' for routine operations. These steps help protect system security and maintain data integrity. [2, 1]