# CVE-2026-50592: Cross-site scripting in Znuny

> Reflected XSS in the AdminCommunicationLog view allows attackers to execute arbitrary scripts in the context of other users.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Jun 2026
- **Updated:** 5 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-50592, GHSA-fjc3-384j-842g, UBUNTU-CVE-2026-50592

## What is CVE-2026-50592?

CVE-2026-50592 is a medium-severity cross-site scripting vulnerability in Znuny, published on 5 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Znuny LTS before 6.5.21 and Znuny before 7.3.3, there is reflected XSS in 

AdminCommunicationLog (aka the communication log administration view).

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

Upgrade to a fixed version.

## Is CVE-2026-50592 being exploited?

There is no known exploitation of CVE-2026-50592 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50592 is a medium-severity cross-site scripting vulnerability in Znuny, published on 5 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-50592 in the wild and no public exploit code.

Affected product: Znuny. 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-50592/ (Markdown: https://insights.sbomify.com/CVE-2026-50592/index.md)
```

## Sources

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

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