dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-13174

HIGH · 8.6 CVSS v3.1 Published 2025-09-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 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 E1 Informatics Web Application allows SQL Injection. This issue affects Web Application: through 20250916.  NOTE: The vendor did not inform about the completion of the fixing process within the specified time. The CVE will be updated when new information becomes available.

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 E1 Informatics Web Application allows attackers to inject malicious SQL commands through unsanitized user input. The vulnerability affects the web application through version 20250916.

MitigationImplement parameterized queries or prepared statements for all database interactions. Validate and sanitize all user inputs before using them in SQL queries. Apply vendor patches when available.

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
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

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 E1 Informatics Web Application installation
    Locate the application binaries, configuration files, or web interface. Check for files named 'e1', 'e1informatics', or check the web server's deployed applications list.
    Affected if The application is E1 Informatics Web Application and version cannot be determined or is <= 20250916
  2. Determine installed version
    Check application version through: 1) Login to the web interface and view the 'About' or 'System Information' page, 2) Check version files in the application directory (such as version.txt, VERSION, or build.info), 3) Query the application's database or admin panel for version information.
    Affected if The installed version is 20250916 or earlier, or the version cannot be verified and the application is confirmed as E1 Informatics Web Application
  3. Inspect database configuration for input handling
    Examine database configuration files (such as dbconfig.xml, database.yml, or connection strings) in the application directory. Look for patterns indicating dynamic SQL query construction versus parameterized queries.
    Affected if The application uses string concatenation or unsanitized string formatting to build SQL queries with user-supplied input
  4. Check for unsanitized user input in SQL code
    Review application source code, stored procedures, or configuration files for SQL query patterns. Look for code sections that accept user parameters and directly insert them into SQL statements without using prepared statements, parameterized queries, or input sanitization functions.
    Affected if Code or configuration files show user input being directly concatenated into SQL queries without sanitization or parameter binding
  5. Review application logs for SQL injection attempts
    Examine web application logs, database audit logs, or security event logs for suspicious SQL patterns. Search for common SQL injection payloads (such as 'UNION SELECT', '1=1', '; DROP, or common SQL functions in user-supplied fields).
    Affected if Logs contain SQL injection signatures or abnormal SQL query patterns originating from user input fields

The environment is affected if E1 Informatics Web Application version 20250916 or earlier is installed AND the application processes user input in SQL queries without proper sanitization or parameterized queries.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries or prepared statements for all database interactions. Validate and sanitize all user inputs before using them in SQL queries. Apply vendor patches when available.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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