CVE-2025-7169
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-7169 is a critical SQL injection vulnerability in version 1.0 of the Crime Reporting System, specifically in the /complainer_page.php file. It occurs because the 'location' 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 gaining unauthorized access to the database, reading, modifying, or deleting sensitive data. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, data tampering, and full system control by attackers. It can compromise the confidentiality, integrity, and availability of the system, potentially causing service disruption and loss or alteration of sensitive information. [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 'location' parameter in the /complainer_page.php file for SQL injection. A proof-of-concept payload uses a time-based blind SQL injection with a SLEEP command to confirm the vulnerability. For example, sending a POST request with the payload: location=Anandapur' (SELECT 0x6354694b WHERE 8181=8181 AND (SELECT 5933 FROM (SELECT(SLEEP(5)))ueEC)) '&type_crime=Pick Pocket&d_o_c=2025-06-18&description=11111&s=Submit can indicate the vulnerability if the response is delayed. Additionally, the sqlmap tool can be used to automate detection and exploitation of this SQL injection vulnerability by targeting the 'location' parameter on the vulnerable URL. [3, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to separate SQL code from user input, preventing injection. 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 database operations. 4) Conduct regular security audits of code and systems to detect and address vulnerabilities promptly. If possible, replace the affected component with an alternative product as no known mitigations or countermeasures have been documented. [3, 2]