# CVE-2020-15924: SQL injection in n/a

> Unauthenticated SQL injection in Mida eFramework allows attackers to disclose sensitive information via authentication parameters.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 24 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9h84-2w3v-5r29

## What is CVE-2020-15924?

CVE-2020-15924 is a high-severity SQL injection vulnerability in n/a, published on 24 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is a SQL Injection in Mida eFramework through 2.9.0 that leads to Information Disclosure. No authentication is required. The injection point resides in one of the authentication parameters.

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

## Which versions are affected by CVE-2020-15924?

It affects 1 product.


Products: Midasolutions Eframework.

## How do I fix CVE-2020-15924?

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

## Is CVE-2020-15924 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-15920](https://insights.sbomify.com/CVE-2020-15920/): Command injection in n/a (critical 9.8)
- [CVE-2020-15921](https://insights.sbomify.com/CVE-2020-15921/): Auth bypass in n/a (critical 9.8)
- [CVE-2020-15922](https://insights.sbomify.com/CVE-2020-15922/): Command injection in n/a (critical 9.8)
- [CVE-2020-15923](https://insights.sbomify.com/CVE-2020-15923/): Path traversal in n/a (high 7.5)
- [CVE-2020-15919](https://insights.sbomify.com/CVE-2020-15919/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-15924 and fix it if it is affected.

What it is: CVE-2020-15924 is a high-severity SQL injection vulnerability in n/a, published on 24 Jul 2020. 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-2020-15924 in the wild and no public exploit code.

Affected product: n/a. 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-2020-15924/ (Markdown: https://insights.sbomify.com/CVE-2020-15924/index.md)
```

## Sources

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

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