# CVE-2024-41973: WAGO: Remote Arbitrary File Write with Root Privileges in multiple Devices

> A low-privileged remote attacker can write arbitrary files with root privileges on WAGO industrial controllers, potentially leading to full system compromise.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Nov 2024
- **Updated:** 27 Aug 2025
- **Also known as:** GHSA-jw5r-wxx3-rm98

## What is CVE-2024-41973?

CVE-2024-41973 is a high-severity path traversal vulnerability in WAGO CC100 0751-9x01, published on 18 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A low privileged remote attacker can specify an arbitrary file on the filesystem which may lead to an arbitrary file writes with root privileges.

Weakness: CWE-35 (Path Traversal: '.../...//')

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


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

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

## Is CVE-2024-41973 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-41973 is a high-severity path traversal vulnerability in WAGO CC100 0751-9x01, published on 18 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-41973 in the wild and no public exploit code.

Affected product: WAGO CC100 0751-9x01. 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-41973/ (Markdown: https://insights.sbomify.com/CVE-2024-41973/index.md)
```

## Sources

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

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