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

> An authenticated attacker can upload a malicious PHP file to the profile page, resulting in remote code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2022
- **Updated:** 21 May 2025
- **Also known as:** GHSA-4rhp-v69r-6w59

## What is CVE-2022-40878?

CVE-2022-40878 is a high-severity vulnerability in n/a, published on 27 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Exam Reviewer Management System 1.0, an authenticated attacker can upload a web-shell php file in profile page to achieve Remote Code Execution (RCE).

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

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

It affects 1 product.


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

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

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

## Is CVE-2022-40878 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-40878 is a high-severity vulnerability in n/a, published on 27 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-40878 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-40878/ (Markdown: https://insights.sbomify.com/CVE-2022-40878/index.md)
```

## Sources

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

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