# CVE-2024-7074: Authenticated Arbitrary File Upload in Multiple WSO2 Products via SOAP Admin Service Leading to Remote Code Execution

> Authenticated attackers with admin privileges can upload arbitrary files to achieve remote code execution on WSO2 servers.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2025
- **Updated:** 2 Jun 2025
- **Also known as:** GHSA-7f34-p2r4-j656

## What is CVE-2024-7074?

CVE-2024-7074 is a medium-severity vulnerability in WSO2 API Manager, published on 2 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An arbitrary file upload vulnerability exists in multiple WSO2 products due to improper validation of user input in SOAP admin services. A malicious actor with administrative privileges can upload an arbitrary file to a user-controlled location on the server.

By leveraging this vulnerability, an attacker could upload a specially crafted payload, potentially achieving remote code execution (RCE) on the server. Exploitation requires valid admin credentials, limiting its impact to authorized but potentially malicious users.

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

## Which versions are affected by CVE-2024-7074?


## How do I fix CVE-2024-7074?

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

## Is CVE-2024-7074 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-7074 and fix it if it is affected.

What it is: CVE-2024-7074 is a medium-severity vulnerability in WSO2 API Manager, published on 2 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-7074 in the wild and no public exploit code.

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

## Sources

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

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