CVE-2025-49182VulnerabilityPublished 12 Jun 2025Updated 16 Jun 2025

CVE-2025-49182: SICK Media Server · Inclusion of Sensitive Information in Source Code

Affects SICK Media ServerSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.5High

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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-26.

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 Media Server	Affected =0	Fixed in–

AI-suggested

1. Immediate mitigation should include auditing all deployments of SICK Media Server to identify affected versions, especially early or initial releases. 2. Since no official patches are available yet, organizations should implement network-level access controls to restrict access to the media server only to trusted internal hosts and networks, using firewalls and segmentation. 3. Change default or hardcoded credentials if possible by accessing configuration files or management interfaces, or by reinstalling the software with secure credentials if supported. 4. Monitor network traffic and logs for any unauthorized access attempts or suspicious activity targeting the media server. 5. Engage with SICK AG support channels to obtain information on upcoming patches or security advisories and apply updates promptly once available. 6. Consider deploying intrusion detection/prevention systems (IDS/IPS) with signatures or anomaly detection tuned for media server protocols to detect exploitation attempts. 7. For critical environments, consider isolating the media server from internet-facing networks and limit administrative access to dedicated management networks. 8. Conduct security awareness training for administrators managing these systems to recognize and respond to potential exploitation attempts. 9. Review and enhance overall credential management policies to prevent embedding sensitive credentials in source code or configuration files in future deployments.

Description

Files in the source code contain login credentials for the admin user and the property configuration password, allowing an attacker to get full access to the application.

Impact

For European organizations, the impact of CVE-2025-49182 can be significant, especially for those using SICK Media Server in industrial automation, manufacturing, or logistics sectors where SICK AG products are commonly deployed. Unauthorized access to the media server could lead to exposure of sensitive operational data, intellectual property, or surveillance media. Attackers gaining admin access could manipulate or disrupt media streams, potentially affecting real-time monitoring or control systems. This could result in operational downtime, loss of data confidentiality, and potential compliance violations under GDPR if personal data is processed or stored. Furthermore, compromised media servers could serve as pivot points for lateral movement within corporate networks, increasing the risk of broader network compromise. The lack of integrity and availability impact in the CVSS vector suggests that while data confidentiality is at high risk, the system’s operation and data integrity may not be directly affected by this vulnerability alone. However, attackers with admin access could still perform malicious actions beyond the scope of this vulnerability. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, especially as threat actors often reverse-engineer disclosed vulnerabilities to develop exploits. European organizations relying on SICK Media Server should consider this vulnerability a critical security concern due to the ease of exploitation and the high confidentiality impact.

CWE-540Inclusion of Sensitive Information in Source Code (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
Source code on a web server or repository often contains sensitive information and should generally not be accessible to users.
Architecture and Design · System Configuration
Recommendations include removing this script from the web server and moving it to a location not accessible from the Internet.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (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, 13:38 UTC

WeaknessesCWE-540

Technical details

References

Community reviews

Related threats