# CVE-2022-27925: Synacor Zimbra Collaboration Suite (ZCS) Arbitrary File Upload

> An authenticated administrator can exploit directory traversal in mboximport to upload arbitrary files, potentially leading to code execution.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 11 Aug 2022 (CISA KEV), used in ransomware
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Apr 2022
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-j5r7-6rm3-99mm

## What is CVE-2022-27925?

CVE-2022-27925 is a high-severity path traversal vulnerability in Synacor Zimbra Collaboration Suite, published on 20 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Zimbra Collaboration (aka ZCS) 8.8.15 and 9.0 has mboximport functionality that receives a ZIP archive and extracts files from it. An authenticated user with administrator rights has the ability to upload arbitrary files to the system, leading to directory traversal.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2022-27925?

It affects 1 product.


Products: Synacor Zimbra Collaboration Suite.

## How do I fix CVE-2022-27925?

No fix has been published for CVE-2022-27925 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 1 Sep 2022.

## Is CVE-2022-27925 being exploited?

Yes. Attackers have exploited CVE-2022-27925 in the wild since at least 11 Aug 2022, including in ransomware campaigns.

Public exploit code:

- Zimbra RCE simple poc (github_poc): https://github.com/vnhacker1337/CVE-2022-27925-PoC
- Zimbra CVE-2022-27925 PoC (github_poc): https://github.com/Josexv1/CVE-2022-27925
- A loader for zimbra 2022 rce (cve-2022-27925) (github_poc): https://github.com/sh4den/CVE-2022-27925
- CVE-2022-27925 (github_poc): https://github.com/jam620/Zimbra
- Python Script to exploit Zimbra Auth Bypass + RCE (CVE-2022-27925) (github_poc): https://github.com/Chocapikk/CVE-2022-27925-Revshell
- CVE-2022-27925 nuclei template (github_poc): https://github.com/akincibor/CVE-2022-27925

## 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-2022-27925 and fix it if it is affected.

What it is: CVE-2022-27925 is a high-severity path traversal vulnerability in Synacor Zimbra Collaboration Suite, published on 20 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-27925 in the wild since at least 11 Aug 2022, including in ransomware campaigns.

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-2022-27925/ (Markdown: https://insights.sbomify.com/CVE-2022-27925/index.md)
```

## Sources

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

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