CVE-2025-7168
BaseFortify
Publication date: 2025-07-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 | crime_reporting_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-7168 is a critical SQL injection vulnerability in the Crime Reporting System version 1.0, specifically in the /userlogin.php file. It occurs because the application does not properly validate or sanitize the 'email' parameter from user input, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized database access, leakage of sensitive information, data tampering or deletion, potential full system control by attackers, and possible service interruptions. Because it can be exploited remotely without authentication, it poses a high risk to system security and data integrity. [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 identifying the presence of the vulnerable endpoint /userlogin.php and testing the 'email' parameter for SQL injection. One method is to use Google Dorking with queries like 'inurl:userlogin.php' to find potentially vulnerable targets. Additionally, manual or automated SQL injection testing tools can be used to send crafted inputs to the 'email' parameter and observe if SQL errors or unexpected behavior occurs. Specific commands depend on the tools used, but examples include using curl or sqlmap to test the parameter, e.g., 'sqlmap -u "http://target/userlogin.php?email=test" --batch'. [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 known mitigations are documented. 2) If replacement is not feasible, apply secure coding practices such as using prepared statements to handle the 'email' parameter, ensuring inputs are treated as data and not executable SQL. 3) Implement strict input validation and filtering on the 'email' parameter to allow only expected formats. 4) Minimize database user permissions by avoiding high-privilege accounts for routine operations. 5) Conduct regular security audits to detect and fix vulnerabilities promptly. [2, 3]