# CVE-2021-46013: File upload in n/a

> An attacker can upload a malicious PHP webshell to the school management software, enabling remote code execution 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:** 18 Jan 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cp62-q7v3-5q5w

## What is CVE-2021-46013?

CVE-2021-46013 is a critical vulnerability in n/a, published on 18 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unrestricted file upload vulnerability exists in Sourcecodester Free school management software 1.0. An attacker can leverage this vulnerability to enable remote code execution on the affected web server. Once a php webshell containing "<?php system($_GET["cmd"]); ?>" gets uploaded it is saved into /uploads/exam_question/ directory, and is accessible by all users.

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

## Which versions are affected by CVE-2021-46013?

It affects 1 product.


Products: Free School Management Software Project Free School Management Software.

## How do I fix CVE-2021-46013?

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

## Is CVE-2021-46013 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-46013 and fix it if it is affected.

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

## Sources

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

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