# CVE-2024-45519: Synacor Zimbra Collaboration Suite (ZCS) Command Execution

> Unauthenticated attackers can execute arbitrary commands via the postjournal service in Zimbra Collaboration.

- **Severity:** Critical 10.0 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:C/UI:N`)
- **Exploited in the wild:** Yes, since 3 Oct 2024 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2024
- **Updated:** 3 Feb 2026
- **Also known as:** CVE-2025-71275, GHSA-fr4c-ch83-r968

## What is CVE-2024-45519?

CVE-2024-45519 is a critical command injection vulnerability in Synacor Zimbra Collaboration Suite, published on 2 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The postjournal service in Zimbra Collaboration (ZCS) before 8.8.15 Patch 46, 9 before 9.0.0 Patch 41, 10 before 10.0.9, and 10.1 before 10.1.1 sometimes allows unauthenticated users to execute commands.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2024-45519?

It affects 1 product.


Products: Synacor Zimbra Collaboration Suite.

## How do I fix CVE-2024-45519?

No fix has been published for CVE-2024-45519 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 24 Oct 2024.

## Is CVE-2024-45519 being exploited?

Yes. Attackers have exploited CVE-2024-45519 in the wild since at least 3 Oct 2024.

Public exploit code:

- Zimbra - Remote Command Execution (CVE-2024-45519) (github_poc): https://github.com/Chocapikk/CVE-2024-45519
- https://github.com/p33d/CVE-2024-45519 (github_poc): https://github.com/p33d/CVE-2024-45519
- Zimbra CVE-2024-45519 (github_poc): https://github.com/sec13b/CVE-2024-45519
- Zimbra CVE-2024-45519 real fix - Official patch is incomplete (github_poc): https://github.com/lionels-cyber/CVE-2024-45519-Zimbra-Real-Fix
- Zimbra Collaboration Suite < 9.0.0 - Remote Code Execution (nuclei)

## Other vulnerabilities in Synacor Zimbra Collaboration Suite

- [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)
- [CVE-2019-9670](https://insights.sbomify.com/CVE-2019-9670/): Synacor Zimbra Collaboration Suite (ZCS) Improper Restriction of XML External Entity Reference (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-45519 and fix it if it is affected.

What it is: CVE-2024-45519 is a critical command injection vulnerability in Synacor Zimbra Collaboration Suite, published on 2 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2024-45519 in the wild since at least 3 Oct 2024.

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

## Sources

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

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