CVE-2025-49181: SICK Media Server · Missing Authorization
Affects SICK Media ServerSource CVE Database V5
Not known to be exploited · CVSS 8.6 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 34% 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:L/A:HExploitation 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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SICK AG SICK Media Server | Affected
| Fixed in– |
AI-suggested
1. Immediate Network Segmentation: Isolate the SICK Media Server instances within dedicated network segments with strict access controls to limit exposure to untrusted networks, especially the internet. 2. Implement Web Application Firewalls (WAF): Deploy WAFs capable of detecting and blocking unauthorized HTTP requests targeting the vulnerable API endpoints, focusing on anomalous POST requests attempting to modify configuration parameters. 3. Access Control via Network Policies: Restrict access to the media server’s management interfaces to authorized IP addresses or VPN connections only, reducing the attack surface. 4. Monitor and Alert: Establish monitoring on the media server’s API endpoints for unusual GET or POST requests, particularly those attempting to change log paths or TCP ports, and configure alerts for such activities. 5. Temporary Disablement: If feasible, disable or restrict the vulnerable API endpoints until a vendor patch is available. 6. Vendor Engagement: Engage with SICK AG for timelines on patch releases and request interim mitigations or configuration changes that can reduce risk. 7. Incident Response Preparedness: Prepare incident response plans specific to potential DoS or data leakage scenarios involving the media server. 8. Regular Auditing: Conduct frequent audits of the media server’s configuration and logs to detect unauthorized changes early. 9. Network Intrusion Detection Systems (NIDS): Deploy NIDS with signatures or heuristics to detect exploitation attempts targeting this vulnerability. These recommendations go beyond generic advice by focusing on network-level controls, monitoring specific to the vulnerability’s exploitation vectors, and operational readiness in industrial environments.
Description
Due to missing authorization of an API endpoint, unauthorized users can send HTTP GET requests to gather sensitive information. An attacker could also send HTTP POST requests to modify the log files’ root path as well as the TCP ports the service is running on, leading to a Denial of Service attack.
References
- sick.com/psirt (opens in a new tab)
- cdn.sick.com/media/docs/1/11/411/Special_information_CYBERSECURITY_BY_SICK_en_IM0084411.PDF (opens in a new tab)
- cisa.gov/resources-tools/resources/ics-recommended-practices (opens in a new tab)
- first.org/cvss/calculator/3.1 (opens in a new tab)
- sick.com/.well-known/csaf/white/2025/sca-2025-0007.pdf (opens in a new tab)
- sick.com/.well-known/csaf/white/2025/sca-2025-0007.json (opens in a new tab)