# CVE-2024-34021: File upload in WMC-2LX-B

> An authenticated administrator can upload a malicious file to ELECOM routers to execute arbitrary OS commands.

- **Severity:** Medium 6.8 (`CVSS:3.0/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:** 1 Aug 2024
- **Updated:** 12 May 2026
- **Also known as:** GHSA-p2wx-946c-4xxv

## What is CVE-2024-34021?

CVE-2024-34021 is a medium-severity vulnerability in ELECOM CO.,LTD. WMC-2LX-B, published on 1 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unrestricted upload of file with dangerous type vulnerability exists in ELECOM wireless LAN routers. A specially crafted file may be uploaded to the affected product by a logged-in user with an administrative privilege, resulting in an arbitrary OS command execution.

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

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


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

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

## Is CVE-2024-34021 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-34021 is a medium-severity vulnerability in ELECOM CO.,LTD. WMC-2LX-B, published on 1 Aug 2024. 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-34021 in the wild and no public exploit code.

Affected product: ELECOM CO.,LTD. WMC-2LX-B. 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-34021/ (Markdown: https://insights.sbomify.com/CVE-2024-34021/index.md)
```

## Sources

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

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