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 10 Mar 2026.
Zimbra Collaboration SuiteApplication · Synacor

CVE-2020-7796

CRITICAL · 9.8 CVSS v3.1 Published 2020-02-18
Fix available
A fix is available. Upgrade to 8.8.15 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges 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
Zimbra Collaboration Suite (ZCS) before 8.8.15 Patch 7 allows SSRF when WebEx zimlet is installed and zimlet JSP is enabled.

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

Server-Side Request Forgery (SSRF) vulnerability in Zimbra Collaboration Suite affecting versions prior to 8.8.15 Patch 7. The flaw exists specifically when the WebEx zimlet is installed and the zimlet JSP functionality is enabled, allowing remote attackers to coerce the server into making arbitrary HTTP requests to internal resources or external systems.

MitigationUpgrade ZCS to version 8.8.15 Patch 7 or later. Alternatively, if the WebEx zimlet is not required, uninstall it or disable zimlet JSP functionality as an interim workaround.

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:< 8.8.15= 8.8.15

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 the installed Zimbra Collaboration Suite version
    Run 'zmcontrol -v' or check the installed package version (e.g., 'rpm -q zimbra-core' or 'apt list --installed | grep zimbra'). Compare the version number to the affected range: versions before 8.8.15, or version 8.8.15 without Patch 7.
    Affected if The installed version is below 8.8.15, or is exactly 8.8.15 without the Patch 7 update.
  2. Determine whether the WebEx zimlet is installed
    List installed zimlets via the Zimbra admin console, or check the zimlets directory (typically /opt/zimbra/zimlets/) for a 'com_zimbra_webex' or similar WebEx-related zimlet folder. You can also run 'zmprov gacf | grep zimlet' to list configured zimlets.
    Affected if The WebEx zimlet package is present on the server.
  3. Verify whether zimlet JSP functionality is enabled
    Check the Zimbra server configuration for the zimlet JSP feature. This is typically controlled via the 'zimlet JSP' attribute in the server settings (zmprov gacf or zmprov gs <server>). Alternatively, inspect the zimlet configuration XML files in the zimlet directory to see if JSP handling is active.
    Affected if Zimlet JSP processing is enabled in the ZCS configuration.

A server is affected only if it runs a vulnerable ZCS version (below 8.8.15 or 8.8.15 without Patch 7), has the WebEx zimlet installed, AND has zimlet JSP functionality enabled.

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
Upgrade available Upgrade to 8.8.15 or later
Fixed in 8.8.15
Interim mitigation

Upgrade ZCS to version 8.8.15 Patch 7 or later. Alternatively, if the WebEx zimlet is not required, uninstall it or disable zimlet JSP functionality as an interim workaround.

Recommended fix High confidence

ZCS 8.8.15 Patch 7 or later

  1. Confirm the current Zimbra Collaboration Suite version by running: zmcontrol -v
  2. If running ZCS 8.8.15, apply Patch 7 by downloading it from the Zimbra patch repository or Zimbra's official support channels
  3. If running a version less than 8.8.15, upgrade to ZCS 8.8.15 Patch 7 or later
  4. After patching, verify the WebEx zimlet configuration and ensure zimlet JSP is properly secured
  5. Restart Zimbra services to apply changes: zmcontrol restart
Caveat Patch application may require service downtime; test in staging environment 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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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