# CVE-2022-27261: Express-FileUpload Arbitrary File Overwrite

> Attackers can overwrite server files by uploading multiple files with identical names in Express-FileUpload.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-w4m6-x6c2-j5c9, MINI-fvfc-rpp5-982c

## What is CVE-2022-27261?

CVE-2022-27261 is a high-severity vulnerability in n/a, published on 12 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An arbitrary file write vulnerability in Express-FileUpload v1.3.1 allows attackers to upload multiple files with the same name, causing an overwrite of files in the web application server.

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

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

2 open source packages ship an affected version, including express-fileupload. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `express-fileupload` | npm | All versions to 1.3.1 | None |
| `express-fileupload` | npm | All versions to 1.3.1 | None |

Products: Express-Fileupload Project Express-Fileupload.

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

Upgrade to a fixed version.

## Is CVE-2022-27261 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-27140](https://insights.sbomify.com/CVE-2022-27140/): File upload in n/a (critical 9.8)
- [CVE-2020-7699](https://insights.sbomify.com/CVE-2020-7699/): Prototype Pollution (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-27261 is a high-severity vulnerability in n/a, published on 12 Apr 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-2022-27261 in the wild and no public exploit code.

Affected packages and fixed versions:
- express-fileupload (npm): affected all versions up to 1.3.1; no fix listed
- express-fileupload (npm): affected all versions up to 1.3.1; no fix listed

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

## Sources

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

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