# CVE-2024-13174: SQLi in E1 Informatics' Web Application

> An SQL injection vulnerability in E1 Informatics' web application allows attackers to manipulate database queries, potentially exposing or altering sensitive data.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2025
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-ff6p-v237-4x2m

## What is CVE-2024-13174?

CVE-2024-13174 is a high-severity SQL injection vulnerability in E1 Informatics Web Application, published on 16 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2024-13174?


## How do I fix CVE-2024-13174?

No fix has been published for CVE-2024-13174 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-13174 being exploited?

There is no known exploitation of CVE-2024-13174 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-13174 and fix it if it is affected.

What it is: CVE-2024-13174 is a high-severity SQL injection vulnerability in E1 Informatics Web Application, published on 16 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-13174 in the wild and no public exploit code.

Affected product: E1 Informatics Web Application. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-13174/ (Markdown: https://insights.sbomify.com/CVE-2024-13174/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-13174
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-13174
- OSV: https://osv.dev/vulnerability/CVE-2024-13174

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-13174/
Summaries are generated and may contain mistakes; the official description above is the record.