# CVE-2019-5070: SQL injection in Epignosis

> Unauthenticated SQL injection in eFront LMS allows attackers to compromise data via crafted login requests.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-wgfg-7qh2-xjxr

## What is CVE-2019-5070?

CVE-2019-5070 is a medium-severity SQL injection vulnerability in Epignosis, published on 5 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An exploitable SQL injection vulnerability exists in the unauthenticated portion of eFront LMS, versions v5.2.12 and earlier. Specially crafted web request to login page can cause SQL injections, resulting in data compromise. An attacker can use a browser to trigger these vulnerabilities, and no special tools are required.

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

## Which versions are affected by CVE-2019-5070?

It affects 1 product.


Products: Epignosishq Efront Lms.

## How do I fix CVE-2019-5070?

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

## Is CVE-2019-5070 being exploited?

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

## Other vulnerabilities in Epignosis

- [CVE-2019-5069](https://insights.sbomify.com/CVE-2019-5069/): Deserialization in Epignosis (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-5070 and fix it if it is affected.

What it is: CVE-2019-5070 is a medium-severity SQL injection vulnerability in Epignosis, published on 5 Sep 2019. 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-2019-5070 in the wild and no public exploit code.

Affected product: Epignosis. 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-2019-5070/ (Markdown: https://insights.sbomify.com/CVE-2019-5070/index.md)
```

## Sources

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

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