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

> Attackers can achieve remote code execution by uploading malicious files via the admin image upload feature in Simple College Website.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Mar 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-48x2-prxg-j7jq

## What is CVE-2020-28173?

CVE-2020-28173 is a high-severity vulnerability in n/a, published on 31 Mar 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Simple College Website 1.0 allows a user to conduct remote code execution via /alumni/admin/ajax.php?action=save_settings when uploading a malicious file using the image upload functionality, which is stored in /alumni/admin/assets/uploads/.

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

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

It affects 1 product.


Products: Simple College Project Simple College.

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

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

## Is CVE-2020-28173 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-28172](https://insights.sbomify.com/CVE-2020-28172/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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