# CVE-2022-29623: Connect-Multiparty allows arbitrary file upload

> Attackers can execute arbitrary code by uploading a crafted PDF file via the file upload module in Express Connect-Multiparty.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 May 2022
- **Updated:** 20 May 2025
- **Also known as:** GHSA-w2xw-44r3-4v9g

## What is CVE-2022-29623?

CVE-2022-29623 is a high-severity vulnerability in n/a, published on 16 May 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An arbitrary file upload vulnerability in the file upload module of Express Connect-Multiparty 2.2.0 allows attackers to execute arbitrary code via a crafted PDF file. NOTE: the Supplier has not verified this vulnerability report.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `connect-multiparty` | npm | All versions to 2.2.0 | None |
| `connect-multiparty` | npm | All versions to 2.2.0 | None |

Products: Connect-Multiparty Project Connect-Multiparty.

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

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

## Is CVE-2022-29623 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29623 is a high-severity vulnerability in n/a, published on 16 May 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-29623 in the wild and no public exploit code.

Affected packages and fixed versions:
- connect-multiparty (npm): affected all versions up to 2.2.0; no fix listed
- connect-multiparty (npm): affected all versions up to 2.2.0; 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-29623/ (Markdown: https://insights.sbomify.com/CVE-2022-29623/index.md)
```

## Sources

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

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