# CVE-2026-33373: Cross-site request forgery in n/a

> Attackers can bypass CSRF protections to perform sensitive account actions like disabling two-factor authentication in Zimbra Collaboration.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Mar 2026
- **Updated:** 1 Apr 2026
- **Also known as:** GHSA-pqjp-hqqg-x9w2

## What is CVE-2026-33373?

CVE-2026-33373 is a high-severity vulnerability in Synacor Zimbra Collaboration Suite, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in Zimbra Collaboration (ZCS) 10.0 and 10.1. A Cross-Site Request Forgery (CSRF) vulnerability exists in Zimbra Web Client due to the issuance of authentication tokens without CSRF protection during certain account state transitions. Specifically, tokens generated after operations such as enabling two-factor authentication or changing a password may lack CSRF enforcement. While such a token is active, authenticated SOAP requests that trigger token generation or state changes can be performed without CSRF validation. An attacker could exploit this by inducing a victim to submit crafted requests, potentially allowing sensitive account actions such as disabling two-factor authentication. The issue is mitigated by ensuring CSRF protection is consistently enforced for all issued authentication tokens.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-33373?

It affects 1 product.


Products: Synacor Zimbra Collaboration Suite.

## How do I fix CVE-2026-33373?

No fix has been published for CVE-2026-33373 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33373 being exploited?

There is no known exploitation of CVE-2026-33373 in the wild and no public exploit code.

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

What it is: CVE-2026-33373 is a high-severity vulnerability in Synacor Zimbra Collaboration Suite, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-33373 in the wild and no public exploit code.

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

## Sources

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

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