dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-50592

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a reflected Cross-Site Scripting (XSS) vulnerability in Znuny's AdminCommunicationLog component (the communication log administration view). The vulnerability exists in Znuny LTS versions before 6.5.21 and Znuny versions before 7.3.3. An attacker could inject malicious JavaScript into the communication log view that would execute in the browser of an authenticated administrator viewing the logs.

MitigationUpgrade Znuny LTS to version 6.5.21 or later, or Znuny to version 7.3.3 or later to remediate this reflected XSS vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Znuny product and version
    Locate the Znuny installation directory and check the version file (typically Version.pm or a version info file in the root directory). Run: cat /opt/znuny/Version.pm 2>/dev/null || cat /opt/otrs/Version.pm 2>/dev/null || look for a VERSION file in the installation root.
    Affected if The installed version is Znuny LTS below 6.5.21, or Znuny below 7.3.3, or if the version cannot be determined and AdminCommunicationLog is in use.
  2. Verify AdminCommunicationLog module is accessible
    Check SysConfig for the module registration. Look in /opt/znuny/Kernel/System/AdminCommunicationLog.pm or the SysConfig XML files for the AdminCommunicationLog frontend module. Confirm the module is not disabled in the administration panel.
    Affected if The AdminCommunicationLog module is enabled and accessible in the web interface.
  3. Inspect web server access logs for AdminCommunicationLog requests
    Examine the web server logs (Apache/nginx) for requests to index.pl?Action=AdminCommunicationLog. Look for unusual URL parameters that might indicate exploitation attempts, such as suspicious script tags or javascript: in parameter values.
    Affected if Requests to AdminCommunicationLog contain unsanitized user input reflected in the response.
  4. Review browser console for XSS errors
    As an authenticated administrator, navigate to the AdminCommunicationLog page in the web interface. Open browser developer tools and check the console for any XSS-related errors or warnings, and inspect the HTML source of the page for unsanitized parameter reflection.
    Affected if User-supplied parameters in the URL are reflected unescaped in the page HTML.

You are affected if Znuny LTS version is below 6.5.21 or Znuny version is below 7.3.3 AND the AdminCommunicationLog module is enabled and accessible to admin users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Znuny LTS to version 6.5.21 or later, or Znuny to version 7.3.3 or later to remediate this reflected XSS vulnerability.

Recommended fix High confidence

Znuny LTS 6.5.21 or Znuny 7.3.3

  1. 1. Identify the current Znuny installation version (LTS or regular Znuny)
  2. 2. If running Znuny LTS, upgrade to version 6.5.21 or later
  3. 3. If running regular Znuny, upgrade to version 7.3.3 or later
  4. 4. After upgrade, verify the AdminCommunicationLog module is updated by checking the version number in the system
  5. 5. Test that the reflected XSS vulnerability in AdminCommunicationLog is no longer present

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-50592 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-50592 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data