# CVE-2020-19113: File upload in n/a

> An arbitrary file upload vulnerability in the admin panel allows attackers to execute remote code on the server.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 5 May 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q62c-3jf5-pvpj

## What is CVE-2020-19113?

CVE-2020-19113 is a critical vulnerability in n/a, published on 5 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Arbitrary File Upload vulnerability in Online Book Store v1.0 in admin_add.php, which may lead to remote code execution.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Projectworlds Online Book Store Project in Php.

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

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

## Is CVE-2020-19113 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-43155](https://insights.sbomify.com/CVE-2021-43155/): SQL injection in n/a (critical 9.8)
- [CVE-2020-19107](https://insights.sbomify.com/CVE-2020-19107/): SQL injection in n/a (critical 9.8)
- [CVE-2020-19108](https://insights.sbomify.com/CVE-2020-19108/): SQL injection in n/a (critical 9.8)
- [CVE-2020-19109](https://insights.sbomify.com/CVE-2020-19109/): SQL injection in n/a (critical 9.8)
- [CVE-2020-19110](https://insights.sbomify.com/CVE-2020-19110/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-19113 is a critical vulnerability in n/a, published on 5 May 2021. 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-19113 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-19113/ (Markdown: https://insights.sbomify.com/CVE-2020-19113/index.md)
```

## Sources

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

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