dbcve.org
Crime Reporting SystemApplication · Code Projects

CVE-2025-7170

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability classified as critical was found in code-projects Crime Reporting System 1.0. Affected by this vulnerability is an unknown functionality of the file /registration.php. The manipulation of the argument Name leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in Crime Reporting System 1.0's /registration.php allows remote attackers to inject malicious SQL queries through the 'Name' parameter. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries, potentially extracting sensitive data, bypassing authentication, or achieving remote code execution via database features.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries in /registration.php and all other files handling user input. Validate and sanitize all inputs, apply output encoding, and deploy a WAF as a temporary protective measure until the code fix is complete.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Crime Reporting SystemApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Crime Reporting System is installed
    Locate the web application's root directory. Common paths may include /var/www/html/, /www/, or C:\inetpub\wwwroot\. Look for directories containing 'crime', 'reporting', or 'crm' in the name. Check for a file named registration.php in the web root or a subdirectory.
    Affected if The Crime Reporting System version 1.0 is present on the server
  2. Verify the vulnerable registration.php file exists
    Search for the file /registration.php within the application's web directory. On Linux/Unix systems, use: find /var/www -name registration.php 2>/dev/null. On Windows, use dir /s /b registration.php in the web root.
    Affected if The file registration.php exists in the web-accessible directory
  3. Check if the Name parameter handling is vulnerable
    Open registration.php and search for SQL queries that incorporate the 'Name' parameter directly. Look for patterns like $_POST['Name'], $_GET['Name'], or request['Name'] used within SELECT, INSERT, or UPDATE statements without prepare(), bindParam(), or mysqli_stmt_* functions.
    Affected if The code contains SQL queries with the Name parameter concatenated or interpolated without prepared statements
  4. Confirm the application is accessible
    Verify the web server is running and the registration.php endpoint is reachable. Test by accessing http://[your-server]/registration.php or the corresponding path discovered in step 2. A 200 OK response indicates the endpoint is active.
    Affected if The registration.php page loads and accepts input
  5. Determine if user registration is enabled
    Check if the registration functionality is active by examining the application's configuration or attempting to access the registration page. Look for comments or settings that might disable registration in config files or at the top of registration.php.
    Affected if Registration is enabled and the Name field accepts user input

You are affected if Crime Reporting System version 1.0 is installed, the /registration.php file exists, and the code handling the 'Name' parameter uses dynamic SQL queries without parameterized prepared statements.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with prepared statements/parameterized queries in /registration.php and all other files handling user input. Validate and sanitize all inputs, apply output encoding, and deploy a WAF as a temporary protective measure until the code fix is complete.

Fix this in Crime Reporting System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7170 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7170 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data