CVE-2025-7608
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-7608 is a critical SQL injection vulnerability in version 1.0 of the Simple Shopping Cart project, specifically in the /userlogin.php file. The vulnerability occurs because the user_email parameter is not properly validated or sanitized before being used in SQL queries, allowing attackers to inject malicious SQL code. This enables unauthorized manipulation of database queries, potentially leading to unauthorized access, data leakage, data alteration, or deletion. [1, 2]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive information, alteration or deletion of data, full system compromise, and potential service disruptions. Since the attack can be launched remotely without authentication and the exploit is publicly available, it poses a high risk to affected systems. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by scanning for the presence of the vulnerable /userlogin.php file in the Simple Shopping Cart 1.0 application and testing the user_email parameter for SQL injection. Attackers may use Google dorking with queries like "inurl:userlogin.php" to identify vulnerable targets. To detect exploitation attempts or test for the vulnerability, you can use SQL injection testing tools such as sqlmap targeting the user_email parameter. Example command: sqlmap -u "http://targetsite.com/[email protected]" --batch --risk=3 --level=5. Monitoring web server logs for suspicious SQL injection payloads in requests to /userlogin.php can also help detect attacks. [2, 1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying input validation and sanitization to the user_email parameter to prevent SQL injection. The recommended fix is to use prepared statements (parameterized queries) to ensure user inputs are treated as data, not executable SQL code. Additionally, minimize database user permissions by avoiding high-privilege accounts for routine operations. If possible, replace the affected component with an alternative product. Conduct regular security audits to detect and address vulnerabilities promptly. [1, 2]