# CVE-2019-9621: Synacor Zimbra Collaboration Suite (ZCS) Server-Side Request Forgery (SSRF)

> Attackers can exploit a Server-Side Request Forgery vulnerability in the ProxyServlet component to access internal resources or bypass security controls.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Yes, since 7 Jul 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Apr 2019
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-gf2h-5qx6-v9fr

## What is CVE-2019-9621?

CVE-2019-9621 is a high-severity server-side request forgery vulnerability in Synacor Zimbra Collaboration Suite, published on 30 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Zimbra Collaboration Suite before 8.6 patch 13, 8.7.x before 8.7.11 patch 10, and 8.8.x before 8.8.10 patch 7 or 8.8.x before 8.8.11 patch 3 allows SSRF via the ProxyServlet component.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2019-9621?

It affects 1 product.


Products: Synacor Zimbra Collaboration Suite.

## How do I fix CVE-2019-9621?

No fix has been published for CVE-2019-9621 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 28 Jul 2025.

## Is CVE-2019-9621 being exploited?

Yes. Attackers have exploited CVE-2019-9621 in the wild since at least 7 Jul 2025.

Public exploit code:

- Zimbra邮件系统漏洞 XXE/RCE/SSRF/Upload GetShell Exploit  1. (CVE-2019-9621 Zimbra<8.8.11  XXE GetShell Exploit) (github_poc): https://github.com/k8gege/ZimbraExploit
- Zimbra Collaboration Autodiscover Servlet XXE and ProxyServlet SSRF (metasploit)
- Zimbra Collaboration - Autodiscover Servlet XXE and ProxyServlet SSRF (Metasploit) (exploitdb)
- Zimbra Collaboration - Autodiscover Servlet XXE and ProxyServlet SSRF (Metasploit) (exploitdb)
- Zimbra Collaboration - Autodiscover Servlet XXE and ProxyServlet SSRF (Metasploit) (exploitdb)
- Zimbra Collaboration - Autodiscover Servlet XXE and ProxyServlet SSRF (Metasploit) (exploitdb)

## Other vulnerabilities in Synacor Zimbra Collaboration Suite

- [CVE-2024-45519](https://insights.sbomify.com/CVE-2024-45519/): Synacor Zimbra Collaboration Suite (ZCS) Command Execution (critical 10.0, exploited in the wild)
- [CVE-2022-41352](https://insights.sbomify.com/CVE-2022-41352/): Synacor Zimbra Collaboration Suite (ZCS) Arbitrary File Upload (critical 9.8, exploited in the wild)
- [CVE-2022-37042](https://insights.sbomify.com/CVE-2022-37042/): Synacor Zimbra Collaboration Suite (ZCS) Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2022-27924](https://insights.sbomify.com/CVE-2022-27924/): Synacor Zimbra Collaboration Suite (ZCS) Command Injection (critical 9.8, exploited in the wild)
- [CVE-2020-7796](https://insights.sbomify.com/CVE-2020-7796/): Synacor Zimbra Collaboration Suite (ZCS) Server-Side Request Forgery (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-9621 and fix it if it is affected.

What it is: CVE-2019-9621 is a high-severity server-side request forgery vulnerability in Synacor Zimbra Collaboration Suite, published on 30 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2019-9621 in the wild since at least 7 Jul 2025.

Affected product: Synacor Zimbra Collaboration Suite. 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-2019-9621/ (Markdown: https://insights.sbomify.com/CVE-2019-9621/index.md)
```

## Sources

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

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