CVE-2025-49190VulnerabilityPublished 12 Jun 2025Updated 23 Jun 2025

CVE-2025-49190: SICK Field Analytics · Server-Side Request Forgery (SSRF)

Affects SICK Field AnalyticsSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% 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:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
SICK AG SICK Field Analytics	Affected *	Fixed in–

AI-suggested

Implement strict input validation and sanitization on the vulnerable endpoint to ensure that only legitimate and authorized requests are processed, effectively blocking attempts to access internal IP ranges or non-approved ports.

Apply network segmentation and firewall rules to restrict the SICK Field Analytics server's ability to initiate outbound connections to internal services that are not necessary for its operation, minimizing the SSRF attack surface.

Enforce the principle of least privilege by limiting user roles and permissions within the SICK Field Analytics application, ensuring that only trusted users with a genuine need can access the vulnerable functionality.

Monitor and log all outbound requests initiated by the SICK Field Analytics server to detect unusual or unauthorized internal network scanning or access attempts.

Engage with SICK AG to obtain timely patches or updates addressing this vulnerability and plan for rapid deployment once available.

Conduct internal security assessments and penetration tests focusing on SSRF and lateral movement risks within industrial networks to identify and remediate related weaknesses.

Implement multi-factor authentication (MFA) for user access to reduce the risk of credential compromise that could facilitate exploitation.

Use web application firewalls (WAFs) with custom rules to detect and block SSRF attack patterns targeting the vulnerable endpoint.

Description

The application is vulnerable to Server-Side Request Forgery (SSRF). An endpoint can be used to send server internal requests to other ports.

Impact

For European organizations, particularly those in manufacturing, industrial automation, and critical infrastructure sectors, this SSRF vulnerability poses a significant risk. SICK AG is a well-known German company specializing in sensor intelligence and industrial automation solutions, and its products are widely deployed across Europe, especially in Germany, France, Italy, and the Benelux countries. Exploitation of this vulnerability could allow attackers to bypass perimeter defenses and access internal networks that are otherwise isolated, potentially leading to unauthorized disclosure of sensitive operational data or reconnaissance for further attacks. While the immediate impact on integrity and availability is low, the confidentiality breach could expose proprietary analytics data or internal network topology. Additionally, SSRF can be a stepping stone for more severe attacks if combined with other vulnerabilities in internal systems. Given the strategic importance of industrial automation in European manufacturing and critical infrastructure, successful exploitation could disrupt production processes or compromise safety systems indirectly. The requirement for low privileges means that insider threats or compromised user credentials could be leveraged to exploit this vulnerability, increasing the attack surface. The lack of patches and absence of known exploits in the wild currently reduce immediate risk but also highlight the need for proactive mitigation before exploitation becomes widespread.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Jun 2025, 14:38 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats