CVE-2025-7171
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 · uneditedA vulnerability, which was classified as critical, has been found in code-projects Crime Reporting System 1.0. Affected by this issue is some unknown functionality of the file /policelogin.php. The manipulation of the argument email leads to sql injection. The attack may 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 confidenceSQL injection vulnerability in the Crime Reporting System 1.0's policelogin.php file. The 'email' parameter in the login functionality is not properly sanitized, allowing attackers to inject malicious SQL queries. This can lead to unauthorized database access, authentication bypass, and potential data exfiltration.
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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate the vulnerable policelogin.php fileSearch the web server document root for the file 'policelogin.php'. Common paths may include /var/www/html/, /www/, or the application's root directory. Use: find / -name 'policelogin.php' 2>/dev/nullAffected if The file exists on the server - this indicates the Crime Reporting System is installed and may be vulnerable.
-
Confirm the application versionCheck for version information in the application. Look for version.php, readme.txt, or within the source code comments. Search for strings like 'Version', 'v1.0', or check the download/install documentation.Affected if The installed version is Crime Reporting System 1.0 exactly, as this is the only affected version per the CVE.
-
Inspect the email parameter handling in policelogin.phpOpen policelogin.php and locate the login form processing code. Look for the 'email' parameter handling - search for $_POST['email'] or $_GET['email'] usage. Check if the email value is directly concatenated into an SQL query without escaping, parameterization, or use of prepared statements.Affected if The code shows the email parameter is used directly in an SQL query (e.g., "SELECT * FROM users WHERE email = '$email'") without prepared statements, mysqli, or PDO.
-
Test if the login endpoint accepts SQL injectionUsing a tool like Burp Suite or curl, submit a login request with the email parameter set to a test payload such as "' OR '1'='1" or "admin'--". Observe if the application returns unexpected authentication results or database errors.Affected if The application grants access without valid credentials or returns SQL syntax errors, confirming the SQL injection is exploitable.
-
Check web server access logs for SQL injection attemptsReview web server logs (access.log or error.log) in the web server directory for requests to policelogin.php containing SQL metacharacters in the email parameter like quotes, OR, UNION, or comment symbols.Affected if Malicious SQL injection payloads are found in logs, indicating active exploitation attempts.
If the Crime Reporting System version 1.0 is installed, the policelogin.php file exists, and the email parameter is handled with dynamic SQL concatenation without prepared statements, the environment is affected by CVE-2025-7171.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace dynamic SQL queries with parameterized queries (prepared statements) using PDO or mysqli. Additionally, implement input validation and output encoding. Consider applying a web application firewall (WAF) as a temporary mitigation layer.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7171 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-7171 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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