CVE-2026-22919

3.8 LOW

📋 TL;DR

This vulnerability allows attackers with administrative access to inject malicious scripts into the login page, enabling cross-site scripting (XSS) attacks that could steal sensitive user data. Organizations using affected SICK products with administrative interfaces are at risk.

💻 Affected Systems

Products:
  • SICK industrial control systems and devices with web interfaces
Versions: Specific versions not detailed in provided references; consult vendor advisory for exact ranges
Operating Systems: Embedded systems running SICK software
Default Config Vulnerable: ⚠️ Yes
Notes: Requires administrative access to exploit; affects web-based login interfaces in SICK products

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Administrator credentials are stolen via XSS, leading to full system compromise, data exfiltration, and potential lateral movement within the network.

🟠

Likely Case

Session hijacking or credential theft from users accessing the compromised login page, potentially leading to unauthorized access to the system.

🟢

If Mitigated

With proper input validation and output encoding, the attack is prevented, maintaining system integrity and user data security.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires administrative privileges; XSS payloads can be injected into login page fields

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check vendor advisory for specific patched versions

Vendor Advisory: https://sick.com/psirt

Restart Required: Yes

Instructions:

1. Review SICK PSIRT advisory. 2. Download and apply recommended patches. 3. Restart affected systems. 4. Verify fix implementation.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement server-side input validation and output encoding for all user-controllable inputs on login page

Content Security Policy (CSP)

all

Deploy CSP headers to restrict script execution sources and mitigate XSS impact

🧯 If You Can't Patch

  • Restrict administrative access to trusted networks only
  • Implement web application firewall (WAF) rules to block XSS payloads

🔍 How to Verify

Check if Vulnerable:

Test login page inputs for XSS vulnerabilities using security testing tools; check if administrative inputs are properly sanitized

Check Version:

Check system firmware/software version through device web interface or CLI

Verify Fix Applied:

Verify that malicious script inputs are properly sanitized and do not execute in the login page

📡 Detection & Monitoring

Log Indicators:

  • Unusual administrative login activity
  • Suspicious input patterns in web server logs
  • JavaScript execution errors in browser logs

Network Indicators:

  • HTTP requests with suspicious script tags or encoded payloads to login endpoints

SIEM Query:

source="web_server" AND (uri="/login" OR uri="/auth") AND (content CONTAINS "<script>" OR content CONTAINS "javascript:")

🔗 References

📤 Share & Export