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

> An attacker can execute arbitrary SQL commands via the admin/mobile.php endpoint in Gambio GX, potentially accessing or modifying database contents.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-g2pj-29c7-96vw

## What is CVE-2020-10983?

CVE-2020-10983 is a medium-severity SQL injection vulnerability in n/a, published on 28 Jul 2020. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Gambio GX before 4.0.1.0 allows SQL Injection in admin/mobile.php.

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

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

It affects 1 product.


Products: Gambio Gambio Gx.

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

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

## Is CVE-2020-10983 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-10984](https://insights.sbomify.com/CVE-2020-10984/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2020-10982](https://insights.sbomify.com/CVE-2020-10982/): SQL injection in n/a (medium 4.9)
- [CVE-2020-10985](https://insights.sbomify.com/CVE-2020-10985/): Cross-site scripting in n/a (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-10983 is a medium-severity SQL injection vulnerability in n/a, published on 28 Jul 2020. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-10983 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-10983/ (Markdown: https://insights.sbomify.com/CVE-2020-10983/index.md)
```

## Sources

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

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