CVE-2024-12144
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Finder Fire Safety Finder ERP/CRM (Old System) allows SQL Injection. This issue affects Finder ERP/CRM (Old System): before 18.12.2024.
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 · moderate confidenceA critical SQL injection vulnerability exists in Finder Fire Safety Finder ERP/CRM (Old System) allowing attackers to inject malicious SQL commands via unsanitized input. The flaw has a CVSS score of 9.8 indicating remote, unauthenticated exploitation is possible.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Finder ERP/CRM installationLocate the Finder ERP/CRM (Old System) application in your environment. Determine if you are running the 'Old System' version as opposed to any newer version that may have replaced it.Affected if The organization uses the Finder ERP/CRM Old System version.
-
Check the installed version and build dateAccess the application's 'About' section, help menu, or system information page to find the exact version number and build date. Alternatively, check the installation files or database for version metadata.Affected if The version was released or last updated before 18.12.2024.
-
Determine if the application is exposed to unauthenticated usersReview network exposure settings and authentication requirements. Check whether login pages, API endpoints, or public-facing forms are accessible without authentication.Affected if The application or its input fields are reachable by unauthenticated users over the network.
-
Inspect user input handling in the applicationReview application configuration or proxy logs to observe how user-provided data in login fields, search boxes, or form inputs are processed. Look for indications that inputs are passed directly to database queries.Affected if User inputs are processed without visible use of parameterized queries or input validation routines.
You are likely affected if your environment runs the Finder ERP/CRM Old System with a version or build date prior to 18.12.2024 and the application is accessible to unauthenticated users.
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.
dbcve · scopedApply the vendor patch released on or after 18.12.2024. Until then, validate all user-supplied input and implement parameterized queries to prevent SQL injection.
Apply vendor patch released on/after 18.12.2024
- Contact Finder Fire Safety vendor to request the security patch released on or after December 18, 2024 for the Finder ERP/CRM (Old System)
- Apply the obtained patch to all affected installations
- Verify the patch was successfully applied by testing the previously vulnerable functionality
- Confirm the SQL injection vulnerability is no longer exploitable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12144 — 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-12144 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