Security readout for executives and security teams
Plain-English summary
CVE-2026-22191 affects Beghelli Sicuro24 SicuroWeb. It can let an attacker cause JavaScript to run in an operator’s browser by abusing unsafe AngularJS template rendering. The reported risk is higher where SicuroWeb is accessed over plaintext HTTP or on networks where traffic could be intercepted.
Executive priority
Treat this as a moderate-priority operational technology web risk. Prioritize environments where SicuroWeb is used on shared, untrusted, or plaintext networks. The main business concern is operator-browser compromise through session-level script execution, not direct unauthenticated server takeover based on provided evidence.
Technical view
The issue is AngularJS template injection in SicuroWeb using AngularJS 1.5.2. Untrusted input can be rendered in a template context, allowing arbitrary AngularJS expression execution and resulting JavaScript execution in a user session. CVSS 3.1 is 5.2: adjacent network, low complexity, no privileges, user interaction required, changed scope.
Likely exposure
Organizations using Beghelli Sicuro24 SicuroWeb may be exposed, especially deployments reachable over local or operational networks using plaintext HTTP. The affected version data in the provided record is incomplete, so asset owners should verify exact product versions with Beghelli guidance.
Exploitation context
Public technical writeups and exploit references are listed, but the provided data does not show CISA KEV listing or confirmed active exploitation. Exploitation requires user interaction and an adjacent-network or traffic-injection position, according to the CVSS vector and description.
Researcher notes
Evidence supports AngularJS template injection with browser-side JavaScript execution. Version specificity and vendor remediation status are unclear in the provided sources. Public exploit material is referenced, so defenders should validate exposure carefully without reproducing offensive chains in production.
Mitigation direction
- Check Beghelli advisories or support channels for official fixes or configuration guidance.
- Avoid plaintext HTTP access to SicuroWeb where possible.
- Restrict SicuroWeb access to trusted management networks and operators.
- Monitor operator browsers and SicuroWeb sessions for unexpected script behavior.
- Review whether AngularJS template rendering handles untrusted input safely.
Validation and detection
- Inventory Beghelli Sicuro24 SicuroWeb deployments and exposed interfaces.
- Confirm whether SicuroWeb is reachable over plaintext HTTP.
- Identify the AngularJS version used by deployed SicuroWeb instances.
- Review vendor information for affected versions and remediation status.
- Check logs for suspicious operator-session activity without attempting exploitation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1336: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-22191 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.12.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.2MediumVector: CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.boffsec-services.com/posts/sicuroweb-cve-2026-22191/CVE reference · technical-description, exploit
- https://github.com/kmkz/Exploits/blob/master/2026/CVE-2026-22191-POC.pyCVE reference · exploit
- https://github.com/kmkz/Exploits/blob/master/2026/CVE-2026-22191-SicuroWeb-ATI-chain.txtCVE reference · technical-description
- https://www.beghelli.it/CVE reference · product
- https://www.vulncheck.com/advisories/beghelli-sicuro24-sicuroweb-angularjs-template-injectionCVE reference · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements Used in a Template Engine
Improper Neutralization of Special Elements Used in a Template Engine represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.