CVE-2025-7170
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-7170 is a critical SQL injection vulnerability in version 1.0 of the Crime Reporting System, specifically in the /registration.php file. It occurs because the application improperly handles the 'Name' parameter by using it directly in SQL queries without proper input validation or sanitization. This allows attackers to inject malicious SQL code remotely, leading to unauthorized database access, data leakage, data tampering, and potential full system compromise or service disruption. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive information, modification or deletion of database records, data leakage, and disruption of system services. Attackers can exploit it remotely without authentication, potentially compromising the confidentiality, integrity, and availability of the system, which threatens 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 /registration.php endpoint for SQL injection via the 'Name' parameter. One approach is to use SQL injection testing tools or manual curl commands to inject SQL payloads and observe responses. For example, you can use curl to send a request with a typical SQL injection payload: curl -G 'http://targetsite/registration.php' --data-urlencode "Name=' OR '1'='1" and check if the response indicates a successful injection (e.g., error messages or unexpected data). Additionally, Google dorking with queries like "inurl:registration.php" can help identify potentially vulnerable targets. Automated scanners that test for SQL injection vulnerabilities on the 'Name' parameter in /registration.php can also be used. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements (parameterized queries) to ensure user input is treated as data, not executable SQL code. 2) Strictly validating and sanitizing the 'Name' parameter to allow only expected input formats. 3) Minimizing database user privileges by avoiding use of high-privilege accounts for database operations. 4) Conducting regular security audits and code reviews to detect and fix vulnerabilities promptly. If possible, replacing the affected software with a secure alternative is recommended. [1, 3, 2]