Skip to main content
CVE-2025-49199VulnerabilityPublished Updated

CVE-2025-49199: SICK Field Analytics · Insufficient Verification of Data Authenticity

Affects SICK Field AnalyticsSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
SICK AG SICK Field AnalyticsAffected
  • *
Fixed in–

AI-suggested

Implement strict access controls and monitoring around backup and restore functionalities to ensure only authorized personnel can download or upload backup ZIP files.

Establish integrity verification processes external to the application, such as hashing and signing backup files manually before upload, to detect tampering until an official patch is released.

Monitor network traffic for unusual redirection patterns or connections to unknown external services that could indicate exploitation attempts.

Segment the network to isolate SICK Field Analytics systems from broader corporate networks, limiting the potential for lateral movement.

Conduct regular audits of configuration files and service status to detect unauthorized changes or service disruptions promptly.

Prepare incident response plans specific to this vulnerability, including rollback procedures and forensic analysis capabilities.

Engage with SICK AG for timely updates and patches, and subscribe to their security advisories for rapid deployment once available.

Consider deploying application-layer firewalls or endpoint detection and response (EDR) solutions that can detect anomalous file modifications or service behavior related to the analytics platform.

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.

References

Community reviews

Loading reviews…