VulnerabilityPublished 12 Jun 2025

CVE-2025-49189: SICK Media Server · Sensitive Cookie Without 'HttpOnly' Flag

Affects SICK Media ServerSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

5.3Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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 26 Oct 2026.

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 or the CVSS exploit maturity 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 Media Server	Affected =0	Fixed in–

AI-suggested

Immediate mitigation should focus on configuring the SICK Media Server to set the HttpOnly flag on all sensitive cookies, especially session cookies. This can often be done by updating the web server or application configuration to enforce HttpOnly attributes.
Implement Content Security Policy (CSP) headers to reduce the risk of XSS attacks by restricting the sources of executable scripts.
Conduct thorough input validation and output encoding on all user inputs and outputs to prevent injection of malicious scripts.
Monitor web application logs for unusual activities indicative of attempted XSS or session hijacking.
Restrict access to the media server management interface to trusted networks and use VPNs or other secure access methods.
Employ multi-factor authentication (MFA) for accessing the media server to reduce the impact of stolen session cookies.
Regularly update and patch the SICK Media Server software once the vendor releases a fix addressing this vulnerability.
Educate users and administrators about phishing and social engineering tactics that could facilitate XSS exploitation.
Use web application firewalls (WAFs) with rules designed to detect and block XSS payloads targeting the media server. These steps go beyond generic advice by focusing on specific configurations and layered defenses tailored to the SICK Media Server environment.

Description

The HttpOnlyflag of the session cookie \"@@\" is set to false. Since this flag helps preventing access to cookies via client-side scripts, setting the flag to false can lead to a higher possibility of Cross-Side-Scripting attacks which target the stored cookies.

Impact

For European organizations using the SICK Media Server, this vulnerability poses a risk of session cookie theft through client-side script exploitation. If an attacker successfully exploits this vulnerability, they could hijack user sessions, potentially gaining unauthorized access to the media server's management interface or sensitive operational data. This could lead to unauthorized monitoring, manipulation, or disruption of industrial processes controlled or monitored by the media server. Given that SICK AG is a prominent supplier of industrial automation and sensor solutions widely used in manufacturing, logistics, and process industries across Europe, the confidentiality breach could have operational security implications. However, since the vulnerability does not affect integrity or availability directly, the risk of system downtime or data manipulation is lower. The lack of required user interaction and low attack complexity means that attackers could exploit this vulnerability remotely without needing credentials or user involvement, increasing the threat surface. Organizations in sectors such as manufacturing, automotive, pharmaceuticals, and critical infrastructure that rely on SICK Media Server for industrial monitoring and control could face increased risks of espionage or operational disruption if attackers leverage stolen session cookies to gain persistent access.

Summary

CVE-2025-49189 is a medium-severity vulnerability identified in the SICK Media Server product developed by SICK AG. The vulnerability arises from the improper configuration of the session cookie named "@@", where the HttpOnly flag is set to false. The HttpOnly attribute is a security feature that prevents client-side scripts, such as JavaScript, from accessing cookies. When this flag is not set, it increases the risk that malicious scripts injected via Cross-Site Scripting (XSS) attacks can access session cookies. Although this vulnerability does not directly enable code execution or privilege escalation, it exposes session cookies to theft, which can lead to session hijacking and unauthorized access to user sessions. The CVSS 3.1 base score is 5.3, reflecting a medium severity level, with the vector indicating that the attack can be performed remotely (AV:N), requires low attack complexity (AC:L), no privileges (PR:N), and no user interaction (UI:N). The impact is limited to confidentiality (C:L) with no impact on integrity or availability. No known exploits are currently reported in the wild, and no patches have been published yet. The affected version is listed as "0", which likely indicates an initial or default version of the product. The vulnerability is categorized under CWE-1004, which relates to sensitive cookies without the HttpOnly flag, a common web security misconfiguration that can facilitate cookie theft via XSS attacks. Given the nature of the vulnerability, it is primarily a web application security issue that can be exploited by attackers who can inject or lure users into executing malicious scripts within the context of the SICK Media Server web interface or related web applications.

CWE-1004Sensitive Cookie Without 'HttpOnly' Flag (opens in a new tab)
Variant weaknessLikelihood of exploit: MediumOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The product uses a cookie to store sensitive information, but the cookie is not marked with the HttpOnly flag.
Implementation
Leverage the HttpOnly flag when setting a sensitive cookie in a response.
OWASP Cheat Sheets
Cross-Site Request Forgery Prevention (opens in a new tab)
Session Management (opens in a new tab)
OWASP ASVS 4.0.3
V3.4.2 (opens in a new tab)
V8.3.8 (opens in a new tab)
V13.4.2 (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:39 UTC

WeaknessesCWE-1004

Technical details

References

Community reviews

Related threats