CVE-2025-7172: code-projects Crime Reporting System · SQL Injection
Affects code-projects Crime Reporting SystemSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 8 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| code-projects Crime Reporting System | Affected
| Fixed in– |
AI-suggested
Organizations should immediately audit their deployments of the code-projects Crime Reporting System to identify any instances of version 1.0 in use. Since no official patches are currently available, temporary mitigations include implementing Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the 'email' parameter in /headlogin.php. Input validation and sanitization should be enforced at the application level, ideally by applying parameterized queries or prepared statements if source code access is available. Network segmentation and strict access controls should be applied to limit exposure of the vulnerable system to untrusted networks. Monitoring and logging of all access attempts to the affected endpoint should be enhanced to detect potential exploitation attempts. Organizations should also engage with the vendor or community for updates or patches and plan for an immediate upgrade once a fix is released. Conducting penetration testing focused on SQL injection vectors can help identify residual risks. Finally, sensitive data should be encrypted at rest and in transit to mitigate data exposure risks in case of compromise.
Description
A vulnerability, which was classified as critical, was found in code-projects Crime Reporting System 1.0. This affects an unknown part of the file /headlogin.php. The manipulation of the argument email leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.