# CVE-2025-3626: OS Command Injection via Config Upload in WebUI

> Remote administrators can execute arbitrary OS commands via config upload, gaining full device control.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jul 2025
- **Updated:** 7 Jul 2025
- **Also known as:** GHSA-43fm-wrjr-xr6x

## What is CVE-2025-3626?

CVE-2025-3626 is a critical command injection vulnerability in Frauscher FDS102, published on 7 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A remote attacker with administrator account can gain full control of the device due to improper neutralization of special elements used in an OS Command ('OS Command Injection') while uploading a config file via webUI.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2025-3626 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3626 is a critical command injection vulnerability in Frauscher FDS102, published on 7 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3626 in the wild and no public exploit code.

Affected product: Frauscher FDS102. 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-3626/ (Markdown: https://insights.sbomify.com/CVE-2025-3626/index.md)
```

## Sources

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

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