# CVE-2025-41720: Sauter: Arbitrary File Upload

> A low-privileged attacker can upload arbitrary files to Sauter building automation devices by bypassing extension checks, potentially leading to code execution.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 22 Oct 2025
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-j942-4f9w-rfqh

## What is CVE-2025-41720?

CVE-2025-41720 is a medium-severity vulnerability in Sauter EY-modulo 5 ecos 5 ecos504/505, published on 22 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A low privileged remote attacker can upload arbitrary data masked as a png file to the affected device using the webserver API because only the file extension is verified.

Weakness: CWE-646 (Reliance on File Name or Extension of Externally-Supplied File)

## Which versions are affected by CVE-2025-41720?


## How do I fix CVE-2025-41720?

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

## Is CVE-2025-41720 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-41720 and fix it if it is affected.

What it is: CVE-2025-41720 is a medium-severity vulnerability in Sauter EY-modulo 5 ecos 5 ecos504/505, published on 22 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-41720 in the wild and no public exploit code.

Affected product: Sauter EY-modulo 5 ecos 5 ecos504/505. 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-2025-41720/ (Markdown: https://insights.sbomify.com/CVE-2025-41720/index.md)
```

## Sources

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

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