dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-12918

HIGH · 8.8 CVSS v3.1 Published 2025-02-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Agito Computer Health4All allows SQL Injection. This issue affects Health4All: before 10.01.2025.

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 confidence

SQL injection vulnerability in Agito Computer Health4All allows attackers to inject malicious SQL commands through user-supplied input that is not properly sanitized before being used in database queries. This could enable unauthorized data access, modification, or deletion within the application's database.

MitigationUpgrade to version released on or after January 10, 2025 which contains the patched code. If immediate upgrade is not possible, implement input validation and parameterize all database queries to prevent SQL injection attacks.

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
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 checks

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

  1. Identify installed version of Agito Computer Health4All
    Check the application version information in the software itself, about dialog, or version file typically found in the installation directory
    Affected if Version displays as earlier than 10.01.2025 or the January 10, 2025 release
  2. Locate user input fields in the application
    Review all forms, search boxes, login fields, and parameters passed via URL that accept user input
    Affected if Any input fields exist that interact with database queries without obvious sanitization
  3. Inspect database query implementation
    Examine the application configuration or code files that handle database operations, looking for direct string concatenation in SQL queries versus parameterized queries
    Affected if SQL queries are constructed using string concatenation or unsanitized input rather than parameterized queries or prepared statements
  4. Test input validation in web interfaces or APIs
    If the product exposes a web interface or API, attempt to inject SQL meta-characters (such as single quotes, UNION SELECT, or semicolons) into input fields and observe the response
    Affected if The application returns database errors, unexpected data, or behaves differently when SQL injection payloads are submitted

The environment is affected if the installed Agito Computer Health4All version is prior to the January 10, 2025 release (10.01.2025 or later) and user input fields interact with the database without proper parameterization or sanitization.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version released on or after January 10, 2025 which contains the patched code. If immediate upgrade is not possible, implement input validation and parameterize all database queries to prevent SQL injection attacks.

Recommended fix Low confidence

Health4All version released on or after January 10, 2025 (contact vendor for exact version number)

  1. Contact Agito Computer directly to request the patched version of Health4All released on or after 10.01.2025
  2. Verify with the vendor that the obtained version includes the fix for CVE-2024-12918
  3. After upgrading, confirm the SQL injection vulnerability is resolved through security testing
  4. Ensure the upgrade is performed in a test environment first to validate compatibility with existing systems
Caveat Unknown - contact vendor for upgrade compatibility and migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12918 — 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-2024-12918 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