CVE-2025-7171
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-7171 is a critical SQL injection vulnerability in the Crime Reporting System version 1.0, specifically in the /policelogin.php file. It occurs because the 'email' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can lead to unauthorized access to the database, enabling attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing attackers to gain unauthorized access to your database, leak sensitive information, tamper with or delete data, take full control of the system, and disrupt services. This threatens system security, data integrity, 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 checking for the presence of the vulnerable file /policelogin.php and testing the 'email' parameter for SQL injection. Attackers may locate vulnerable targets using Google dorking with queries like: inurl:policelogin.php. To test on your system, you can use tools like sqlmap or manual curl commands to inject SQL payloads into the 'email' parameter and observe the response for SQL errors or unexpected behavior. For example, a curl command to test might be: curl -G 'http://yourserver/policelogin.php' --data-urlencode "email=' OR '1'='1". Monitoring network traffic for suspicious SQL injection patterns or unexpected database errors can also help detect exploitation attempts. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements (parameterized queries) to ensure user inputs like 'email' are treated as data, not executable SQL code. 2) Implement strict input validation and filtering to ensure inputs conform to expected formats. 3) Minimize database user permissions by avoiding high-privilege accounts for routine operations. 4) Conduct regular security audits of code and systems to detect and remediate vulnerabilities promptly. Additionally, consider replacing the affected software with an alternative product if possible, as no known countermeasures have been reported. These actions will help prevent SQL injection exploitation and protect data integrity. [2, 3]