Beghelli SicuroWeb CVE-2026-41468

Requires adjacent network positioning (AV:A) enabling packet injection or MITM capabilities between operator browsers and SicuroWeb server. Critically depends on plaintext HTTP deployment-HTTPS with proper certificate validation blocks MITM injection vectors. Passive user interaction required (UI:P): operator must browse to a vulnerable SicuroWeb page that processes attacker-injected templates, but this occurs during normal administrative workflows without active social engineering. No authentication prerequisites (PR:N)-exploitation targets the operator's browser session, not server-side authentication. Exploitation success depends on: (1) SicuroWeb deployment over HTTP rather than HTTPS, (2) attacker's ability to intercept or inject traffic on the network segment carrying operator-to-server communications, (3) vulnerable AngularJS 1.5.2 remaining embedded in the deployed SicuroWeb version, (4) presence of exploitable template injection points in the application. Does NOT require: authenticated server access, operator to click malicious links, or social engineering beyond normal application usage. Primary limiting factor is adjacent network requirement-prevents remote internet-based exploitation but allows attacks from compromised devices on building automation networks or via physical network access.

Real-world risk is ELEVATED despite adjacent-network limitation. CVSS 9.3 accurately reflects the severe impact (arbitrary JavaScript execution leading to session takeover), but AV:A constrains the attack surface to network-adjacent positions-typically requiring the attacker to be on the same physical network segment or VLAN as the operator. SSVC framework confirms POC availability (exploitation: poc), total technical impact (complete control of operator session), but marks as non-automatable (requires user interaction for browser execution). The publicly available exploit chain (documented in BoffSec Services writeup and kmkz GitHub POC for CVE-2026-22191, which appears to be the related template injection component) significantly lowers exploitation barriers for attackers already positioned adjacent to target networks. Critical risk factors: (1) plaintext HTTP deployments enable MITM injection without cryptographic barriers, (2) building security systems often operate on isolated networks where 'adjacent' access may be achievable via physical intrusion or compromised IoT devices, (3) operator sessions have elevated privileges for security system management. Mitigating factors: AV:A limits remote internet-based exploitation, UI:P requires operator to trigger the vulnerable code path (though 'passive' interaction suggests normal browsing suffices). Organizations using SicuroWeb in isolated OT/building automation networks face MODERATE risk; those with internet-exposed or shared-network deployments face HIGH risk. No CISA KEV listing suggests targeted rather than widespread exploitation, but POC availability enables rapid weaponization.

An attacker gains adjacent network access to the building automation VLAN (via compromised HVAC controller, rogue wireless AP, or physical Ethernet access in a publicly accessible area). The attacker positions themselves as MITM on plaintext HTTP traffic between an operator's browser and the SicuroWeb server. When the operator navigates to a vulnerable SicuroWeb page, the attacker injects a malicious AngularJS template expression into the HTTP response containing sandbox escape primitives. The operator's browser processes the injected template, escapes the AngularJS sandbox, and executes attacker-controlled JavaScript that exfiltrates session cookies and establishes a persistent WebSocket backdoor for ongoing control. Publicly available POC exists (CVE-2026-22191 exploit chain by kmkz, detailed attack chain documented by BoffSec Services) demonstrating the complete injection-to-execution sequence.