# CVE-2025-49199: Backup files can be modified and uploaded

> Attackers can modify unsigned backup files to disrupt services or redirect internal traffic, impacting industrial analytics operations.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:** 12 Jun 2025
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-4cwc-669q-r7hf

## What is CVE-2025-49199?

CVE-2025-49199 is a high-severity vulnerability in SICK Field Analytics, published on 12 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The backup ZIPs are not signed by the application, leading to the possibility that an attacker can download a backup ZIP, modify and re-upload it. This allows the attacker to disrupt the application by configuring  the  services  in  a  way  that  they  are  unable  to  run,  making  the  application unusable. They can redirect traffic that is meant to be internal to their own hosted services and gathering information.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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

It affects 1 product.


Products: Sick Field Analytics.

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

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

## Is CVE-2025-49199 being exploited?

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

## Other vulnerabilities in SICK Field Analytics

- [CVE-2025-49196](https://insights.sbomify.com/CVE-2025-49196/): Deprecated TLS version supported (medium 6.5)
- [CVE-2025-49200](https://insights.sbomify.com/CVE-2025-49200/): Unencrypted backup contains sensitive information (medium 6.5)
- [CVE-2025-49185](https://insights.sbomify.com/CVE-2025-49185/): Stored Cross-Site-Script (medium 5.5)
- [CVE-2025-49187](https://insights.sbomify.com/CVE-2025-49187/): User enumeration (medium 5.3)
- [CVE-2025-49188](https://insights.sbomify.com/CVE-2025-49188/): Sensitive Data in URL (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-49199 is a high-severity vulnerability in SICK Field Analytics, published on 12 Jun 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-49199 in the wild and no public exploit code.

Affected product: SICK Field Analytics. 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-49199/ (Markdown: https://insights.sbomify.com/CVE-2025-49199/index.md)
```

## Sources

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

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