CVE-2025-7607
BaseFortify
Publication date: 2025-07-14
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 |
|---|---|---|
| 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-7607 is a critical SQL injection vulnerability in Simple Shopping Cart version 1.0, specifically in the /Customers/save_order.php file. It occurs because the 'order_price' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially manipulating the database by reading, modifying, or deleting data. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, allowing attackers to retrieve sensitive information, modify or delete data, disrupt services, and potentially gain full system control. This compromises the confidentiality, integrity, and availability of the affected system, 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 'order_price' parameter in the /Customers/save_order.php endpoint for SQL injection. A proof-of-concept time-based blind SQL injection payload is: order_price=100' AND (SELECT 5582 FROM (SELECT(SLEEP(5)))laoB) AND 'QQhR'='QQhR, which causes a delay in the database response if vulnerable. Tools like sqlmap can be used to automate detection. Additionally, Google dorking with the query inurl:Customers/save_order.php can help identify vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Using prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Implementing strict input validation and filtering on the 'order_price' parameter to ensure it conforms to expected formats. 3) Minimizing database user permissions by avoiding use of high-privilege accounts for routine operations. 4) Conducting regular security audits to detect and address vulnerabilities promptly. If possible, replacing the affected component with an alternative product is also suggested. [2, 3]