# CVE-2022-29464: WSO2 Multiple Products Unrestrictive Upload of File

> Attackers can upload malicious files via directory traversal to achieve remote code execution on WSO2 products.

- **Severity:** Critical 9.8 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Yes, since 25 Apr 2022 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2022
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-mfgw-52pj-hrhg

## What is CVE-2022-29464?

CVE-2022-29464 is a critical vulnerability in Wso2 Api Manager, published on 18 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Certain WSO2 products allow unrestricted file upload with resultant remote code execution. The attacker must use a /fileupload endpoint with a Content-Disposition directory traversal sequence to reach a directory under the web root, such as a ../../../../repository/deployment/server/webapps directory. This affects WSO2 API Manager 2.2.0 up to 4.0.0, WSO2 Identity Server 5.2.0 up to 5.11.0, WSO2 Identity Server Analytics 5.4.0, 5.4.1, 5.5.0 and 5.6.0, WSO2 Identity Server as Key Manager 5.3.0 up to 5.11.0, WSO2 Enterprise Integrator 6.2.0 up to 6.6.0, WSO2 Open Banking AM 1.4.0 up to 2.0.0 and WSO2 Open Banking KM 1.4.0, up to 2.0.0.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 8 products.


Products: Wso2 Api Manager, Wso2 Enterprise Integrator, Wso2 Identity Server, Wso2 Identity Server Analytics, Wso2 Identity Server as Key Manager, Wso2 Open Banking Am, Wso2 Open Banking Iam, Wso2 Open Banking Km.

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

No fix has been published for CVE-2022-29464 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 16 May 2022.

## Is CVE-2022-29464 being exploited?

Yes. Attackers have exploited CVE-2022-29464 in the wild since at least 25 Apr 2022, including in ransomware campaigns.

Public exploit code:

- WSO2 RCE (CVE-2022-29464) exploit and writeup. (github_poc): https://github.com/hakivvi/CVE-2022-29464
- 😭 WSOB is a python tool created to exploit the new vulnerability on WSO2 assigned as CVE-2022-29464. (github_poc): https://github.com/dsssssssm/WSOB
- A bots loader for CVE-2022-29464 with multithreading (github_poc): https://github.com/sh4den/CVE-2022-29464
- Perform With Mass Exploits In WSO Management. (github_poc): https://github.com/Ap0dexMe0/CVE-2022-29464
- RCE exploit for WSO2 (github_poc): https://github.com/gbrsh/CVE-2022-29464
- CVE-2022-29464 PoC for WSO2 products (github_poc): https://github.com/jimidk/Better-CVE-2022-29464

## Other vulnerabilities in Wso2 Api Manager

- [CVE-2024-6914](https://insights.sbomify.com/CVE-2024-6914/): Incorrect Authorization in Multiple WSO2 Products via Account Recovery SOAP Admin Service Leading to Account Takeover (critical 9.8)
- [CVE-2020-13226](https://insights.sbomify.com/CVE-2020-13226/): WSO2 API Manager vulnerable to SSRF (critical 9.8)
- [CVE-2025-2905](https://insights.sbomify.com/CVE-2025-2905/): An XML External Entity (XXE) vulnerability in Multiple WSO2 Products (critical 9.1)
- [CVE-2021-42646](https://insights.sbomify.com/CVE-2021-42646/): XML external entity in n/a (critical 9.1)
- [CVE-2020-24589](https://insights.sbomify.com/CVE-2020-24589/): XML external entity in n/a (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29464 is a critical vulnerability in Wso2 Api Manager, published on 18 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-29464 in the wild since at least 25 Apr 2022, including in ransomware campaigns.

Affected product: Wso2 Api Manager. 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-29464/ (Markdown: https://insights.sbomify.com/CVE-2022-29464/index.md)
```

## Sources

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

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