# CVE-2019-20059: SQL injection in n/a

> Attackers can inject SQL via the sSortDir_0 parameter in YetiShare to extract database information.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Feb 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cjgv-2qcx-q775

## What is CVE-2019-20059?

CVE-2019-20059 is a high-severity SQL injection vulnerability in n/a, published on 10 Feb 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

payment_manage.ajax.php and various *_manage.ajax.php in MFScripts YetiShare 3.5.2 through 4.5.4 directly insert values from the sSortDir_0 parameter into a SQL string. This allows an attacker to inject their own SQL and manipulate the query, typically extracting data from the database, aka SQL Injection. NOTE: this issue exists because of an incomplete fix for CVE-2019-19732.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Mfscripts Yetishare.

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

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

## Is CVE-2019-20059 being exploited?

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

Public exploit code:

- Yetishare SQL Injection in sSortDir_0 parameter - v3.5.2 - v4.5.4. Apart from an admin being able to exploit this, it could also be used in a CSRF attack to trick an admin user into running malicious queries. (github_poc): https://github.com/cve-vuln/CVE-2019-20059

## Other vulnerabilities in n/a

- [CVE-2019-20062](https://insights.sbomify.com/CVE-2019-20062/): Auth bypass in n/a (critical 9.8)
- [CVE-2019-19735](https://insights.sbomify.com/CVE-2019-19735/): Weak cryptography in n/a (critical 9.1)
- [CVE-2019-19734](https://insights.sbomify.com/CVE-2019-19734/): SQL injection in n/a (high 8.8)
- [CVE-2019-19737](https://insights.sbomify.com/CVE-2019-19737/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2019-20060](https://insights.sbomify.com/CVE-2019-20060/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-20059 is a high-severity SQL injection vulnerability in n/a, published on 10 Feb 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-20059 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-2019-20059/ (Markdown: https://insights.sbomify.com/CVE-2019-20059/index.md)
```

## Sources

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

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