CVE-2024-1821
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 was found in code-projects Crime Reporting System 1.0. It has been rated as critical. This issue affects some unknown processing of the file police_add.php. The manipulation of the argument police_name/police_id/police_spec/password leads to sql injection. The exploit has been disclosed to the public and may be used. The identifier VDB-254609 was assigned to this vulnerability.
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 Crime Reporting System 1.0's police_add.php allows attackers to inject malicious SQL code through multiple parameters (police_name, police_id, police_spec, password). The public exploit availability and HIGH CVSS of 8.8 indicate active risk with potential for data exposure or complete database compromise.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Verify Crime Reporting System 1.0 installationLocate the web application directory and confirm the presence of Crime Reporting System files. Check for the existence of police_add.php in the web-accessible path (commonly in /police/ or /includes/ subdirectories).Affected if The file police_add.php exists in the application root or subdirectories, confirming the vulnerable component is present.
-
Identify the application versionLocate and read version.php, README.txt, or any version metadata file within the application root directory to confirm version 1.0.Affected if The installed version is exactly 1.0, matching the affected version range.
-
Inspect police_add.php for vulnerable parametersOpen police_add.php in a text editor or via command line and search for occurrences of the parameters: police_name, police_id, police_spec, and password. Check if these parameters are directly used in SQL queries without prepared statements or parameter binding.Affected if The code contains SQL queries incorporating police_name, police_id, police_spec, or password parameters without using mysqli_prepare(), PDO::prepare(), or similar parameterized query mechanisms.
-
Check for lack of input sanitizationWithin police_add.php, examine how user input is handled. Look for absence of functions like mysqli_real_escape_string(), htmlspecialchars(), or input validation routines before database operations.Affected if No visible input sanitization or validation functions are applied to the SQL parameters before query execution.
A user is affected if they have Code Projects Crime Reporting System version 1.0 with police_add.php present and the code shows direct SQL query construction using the police_name, police_id, police_spec, or password parameters without prepared statements.
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 dataImplement prepared statements/parameterized queries for all database operations in police_add.php and validate/sanitize user inputs before incorporating them into SQL queries. Apply the vendor patch immediately as the exploit is publicly disclosed.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1821 — 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-2024-1821 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