# CVE-2026-41469: Beghelli Sicuro24 SicuroWeb Missing Content Security Policy

> Missing Content Security Policy allows attackers to bypass browser restrictions and execute arbitrary remote scripts in operator sessions.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Apr 2026
- **Updated:** 22 Apr 2026
- **Also known as:** GHSA-vqrw-x4h2-5cgp

## What is CVE-2026-41469?

CVE-2026-41469 is a medium-severity vulnerability in Beghelli SicuroWeb (Sicuro24), published on 22 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Beghelli Sicuro24 SicuroWeb does not enforce a Content Security Policy, allowing unrestricted loading of external JavaScript resources from attacker-controlled origins. When chained with the template injection and sandbox escape vulnerabilities present in the same application, the absence of CSP removes the browser-enforced restriction that would otherwise block external script execution, enabling attackers to load arbitrary remote payloads into operator browser sessions.

Weakness: CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2026-41469?


## How do I fix CVE-2026-41469?

No fix has been published for CVE-2026-41469 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-41469 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41469 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41469 and fix it if it is affected.

What it is: CVE-2026-41469 is a medium-severity vulnerability in Beghelli SicuroWeb (Sicuro24), published on 22 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41469 exists.

Affected product: Beghelli SicuroWeb (Sicuro24). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41469/ (Markdown: https://insights.sbomify.com/CVE-2026-41469/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41469
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41469
- OSV: https://osv.dev/vulnerability/CVE-2026-41469

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41469/
Summaries are generated and may contain mistakes; the official description above is the record.