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

> Authenticated users can upload malicious PHP files via profile picture functionality to achieve remote code execution on the server.

- **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:** 26 May 2021
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-979x-3p5w-qvgc

## What is CVE-2020-26678?

CVE-2020-26678 is a high-severity vulnerability in n/a, published on 26 May 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

vFairs 3.3 is affected by Remote Code Execution. Any user logged in to a vFairs virtual conference or event can abuse the functionality to upload a profile picture in order to place a malicious PHP file on the server and gain code execution.

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

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

It affects 1 product.


Products: Vfairs Vfairs.

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

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

## Is CVE-2020-26678 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-26677](https://insights.sbomify.com/CVE-2020-26677/): SQL injection in n/a (high 8.8)
- [CVE-2020-26680](https://insights.sbomify.com/CVE-2020-26680/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2020-26679](https://insights.sbomify.com/CVE-2020-26679/): Missing authorization in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-26678 is a high-severity vulnerability in n/a, published on 26 May 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-26678 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-26678/ (Markdown: https://insights.sbomify.com/CVE-2020-26678/index.md)
```

## Sources

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

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