# CVE-2022-42201: File upload in n/a

> Attackers can upload malicious files to the Simple Exam Reviewer Management System, potentially leading to remote code execution.

- **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:** 20 Oct 2022
- **Updated:** 8 May 2025
- **Also known as:** GHSA-jxv6-6xm9-8mw3

## What is CVE-2022-42201?

CVE-2022-42201 is a high-severity vulnerability in n/a, published on 20 Oct 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Simple Exam Reviewer Management System v1.0 is vulnerable to Insecure file upload.

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

## Which versions are affected by CVE-2022-42201?

It affects 1 product.


Products: Simple Exam Reviewer Management System Project Simple Exam Reviewer Management System.

## How do I fix CVE-2022-42201?

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

## Is CVE-2022-42201 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-42201 exists.

## Other vulnerabilities in n/a

- [CVE-2022-42198](https://insights.sbomify.com/CVE-2022-42198/): File upload in n/a (high 8.8)
- [CVE-2022-42199](https://insights.sbomify.com/CVE-2022-42199/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2022-42197](https://insights.sbomify.com/CVE-2022-42197/): Privilege escalation in n/a (medium 6.5)
- [CVE-2022-42200](https://insights.sbomify.com/CVE-2022-42200/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-42201 and fix it if it is affected.

What it is: CVE-2022-42201 is a high-severity vulnerability in n/a, published on 20 Oct 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-42201 exists.

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-2022-42201/ (Markdown: https://insights.sbomify.com/CVE-2022-42201/index.md)
```

## Sources

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

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