CVE-2026-41468 | Beghelli SicuroWeb 1.5.2 unmaintained third party components

VDB-359042 · CVE-2026-41468 · GCVE-0-2026-41468 BEGHELLI SICUROWEB 1.5.2 UNMAINTAINED THIRD PARTY COMPONENTS HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 7.1 $0-$5k 2.15+ Summaryinfo A vulnerability described as critical has been identified in Beghelli SicuroWeb 1.5.2. This affects an unknown part. Such manipulation leads to use of unmaintained third party components. This vulnerability only affects products that are no longer supported by the maintainer. This vulnerability is uniquely identified as CVE-2026-41468. The attack can only be initiated within the local network. No exploit exists. Detailsinfo A vulnerability was found in Beghelli SicuroWeb 1.5.2 and classified as critical. Affected by this issue is an unknown code block. The manipulation with an unknown input leads to a use of unmaintained third party components vulnerability. Using CWE to declare the problem leads to CWE-1104. The product relies on third-party components that are not actively supported or maintained by the original developer or a trusted proxy for the original developer. Impacted is confidentiality, integrity, and availability. CVE summarizes: Beghelli Sicuro24 SicuroWeb embeds AngularJS 1.5.2, an end-of-life component containing known sandbox escape primitives. When combined with template injection present in the same application, these primitives allow attackers to escape the AngularJS sandbox and achieve arbitrary JavaScript execution in operator browser sessions, enabling session hijacking, DOM manipulation, and persistent browser compromise. Network-adjacent attackers can deliver the complete injection and escape chain via MITM in plaintext HTTP deployments without active user interaction. The weakness was disclosed by Jean-Marie Bourbon. The advisory is available at boffsec-services.com. This vulnerability is handled as CVE-2026-41468 since 04/20/2026. The exploitation is known to be easy. Access to the local network is required for this attack. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 04/22/2026). There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. Productinfo Vendor Beghelli Name SicuroWeb Version 1.5.2 Support end of life CPE 2.3info 🔒 CPE 2.2info 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 7.1 VulDB Meta Temp Score: 7.1 VulDB Base Score: 5.5 VulDB Temp Score: 5.5 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 8.7 CNA Vector (VulnCheck): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Use of unmaintained third party components CWE: CWE-1104 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Partially Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: no mitigation known Status: 🔍 0-Day Time: 🔒 Timelineinfo 04/20/2026 CVE reserved 04/22/2026 +2 days Advisory disclosed 04/22/2026 +0 days VulDB entry created 04/22/2026 +0 days VulDB entry last update Sourcesinfo Advisory: boffsec-services.com Researcher: Jean-Marie Bourbon Status: Not defined CVE: CVE-2026-41468 (🔒) GCVE (CVE): GCVE-0-2026-41468 GCVE (VulDB): GCVE-100-359042 Entryinfo Created: 04/22/2026 20:55 Changes: 04/22/2026 20:55 (74) Complete: 🔍 Cache ID: 99:5C6:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸