dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 24 Apr 2023.
Zimbra Collaboration SuiteApplication · Synacor

CVE-2022-27926

MEDIUM · 6.1 CVSS v3.1 Published 2022-04-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges

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
A reflected cross-site scripting (XSS) vulnerability in the /public/launchNewWindow.jsp component of Zimbra Collaboration (aka ZCS) 9.0 allows unauthenticated attackers to execute arbitrary web script or HTML via request parameters.

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

A reflected cross-site scripting (XSS) vulnerability exists in the /public/launchNewWindow.jsp component of Zimbra Collaboration Suite 9.0. Attackers can inject arbitrary HTML or JavaScript through unsanitized request parameters, which are reflected back in the response without proper encoding.

MitigationImplement proper input validation and output encoding for all user-supplied parameters in the vulnerable JSP file. Use established encoding libraries appropriate for the HTML context.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Zimbra Collaboration SuiteApplication
Affected:= 9.0.0

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 installed Zimbra version
    Run 'zmcontrol -v' or check /opt/zimbra/.zimbraversion file to determine the exact ZCS version installed
    Affected if Version is 9.0.0 exactly (or falls within the 9.0.0 - 9.0.0 range)
  2. Locate vulnerable JSP component
    Check if /opt/zimbra/jetty/webapps/zimbra/public/launchNewWindow.jsp exists on the server filesystem
    Affected if The file exists and the server runs ZCS 9.0.0
  3. Verify parameter reflection
    Send a crafted request to /public/launchNewWindow.jsp with a test parameter (e.g., ?param=<script>alert(1)</script>) and inspect if the script tags are reflected unescaped in the HTTP response
    Affected if The injected script/HTML is reflected directly in the response without encoding or sanitization
  4. Confirm public access to endpoint
    Verify the /public/launchNewWindow.jsp endpoint is accessible without authentication (no login required)
    Affected if The endpoint is exposed to unauthenticated users

A server is affected if it runs ZCS version 9.0.0 and the /public/launchNewWindow.jsp endpoint reflects unsanitized request parameters back to the client without input validation or output encoding.

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

Implement proper input validation and output encoding for all user-supplied parameters in the vulnerable JSP file. Use established encoding libraries appropriate for the HTML context.

Recommended fix High confidence

ZCS 9.0.0 Patch 30 or later / ZCS 9.0.0 Series Latest Stable

  1. 1. Verify the current ZCS version by running: zmcontrol -v or checking the admin console
  2. 2. Download the latest Zimbra Collaboration Suite 9.0.0 patch or upgrade to a newer stable release (e.g., 9.0.0 Patch 30 or later) from the official Zimbra repository
  3. 3. Before applying the update, perform a full backup of the ZCS environment including configuration, mail stores, and database
  4. 4. Schedule a maintenance window as the upgrade may require service downtime
  5. 5. Apply the patch or upgrade following Zimbra's official upgrade documentation for 9.0.0 series
  6. 6. After upgrade, verify the /public/launchNewWindow.jsp component is no longer vulnerable by testing with a benign XSS payload in the affected parameter
  7. 7. Confirm all ZCS services started successfully post-upgrade
Caveat Review Zimbra release notes for any configuration or feature changes between versions; test in staging before production deployment

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

Fix this in Zimbra Collaboration Suite Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-27926 — 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-2022-27926 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