dbcve.org
Zimbra Collaboration SuiteApplication · Synacor

CVE-2025-32354

HIGH · 8.8 CVSS v3.1 Published 2025-04-29
Fix available
A fix is available. Upgrade to 10.1.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Zimbra Collaboration (ZCS) 9.0 through 10.1, a Cross-Site Request Forgery (CSRF) vulnerability exists in the GraphQL endpoint (/service/extension/graphql) of Zimbra webmail due to a lack of CSRF token validation. This allows attackers to perform unauthorized GraphQL operations, such as modifying contacts, changing account settings, and accessing sensitive user data when an authenticated user visits a malicious website.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A CSRF vulnerability exists in Zimbra Collaboration's GraphQL endpoint (/service/extension/graphql) due to missing CSRF token validation. Attackers can trick authenticated users into executing unauthorized GraphQL operations such as modifying contacts, changing account settings, and exfiltrating sensitive data by luring them to malicious websites.

MitigationImplement CSRF token validation on the GraphQL endpoint and ensure all state-changing operations require valid, per-request tokens that are validated server-side.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Zimbra Collaboration SuiteApplication
Affected:>= 9.0.0, < 10.1.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Zimbra version
    Run 'zmcontrol -v' or 'zmversion' as the zimbra user, or inspect the package version using your system's package manager (e.g., 'rpm -q zimbra-core' or 'dpkg -l zimbra*')
    Affected if The installed version is 9.0.0 through 10.1.3 (any version >= 9.0.0 but < 10.1.4)
  2. Verify GraphQL endpoint is exposed
    Attempt to access 'https://<your-zimbra-host>/service/extension/graphql' via curl or browser while authenticated. A successful HTTP 200 response indicates the endpoint is active
    Affected if The GraphQL endpoint responds and is accessible to authenticated users
  3. Test for CSRF token requirement on GraphQL operations
    Send a GraphQL mutation request (e.g., creating/modifying a contact) to /service/extension/graphql without including any CSRF token (zmcsrf token cookie or request header) and observe if the operation executes successfully
    Affected if State-changing GraphQL operations succeed without requiring a valid CSRF token (no token validation occurs)
  4. Inspect GraphQL endpoint configuration
    Check Zimbra's proxy configuration (nginx/httpd) and the GraphQL endpoint's source code in /opt/zimbra/jetty/webapps/zimbra/public/graphql/ or similar paths for CSRF validation logic
    Affected if No CSRF token validation code is present in the GraphQL endpoint handling

You are affected if your Zimbra version is between 9.0.0 and 10.1.3 and the GraphQL endpoint accepts state-changing requests without validating CSRF tokens.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.1.4 or later
Fixed in 10.1.4
Interim mitigation

Implement CSRF token validation on the GraphQL endpoint and ensure all state-changing operations require valid, per-request tokens that are validated server-side.

Recommended fix High confidence

10.1.4 or later

  1. 1. Verify the current Zimbra Collaboration Suite version by running: zmcontrol -v or su - zimbra -c 'zmcontrol -v'
  2. 2. Take a complete backup of the Zimbra server including the database, configuration files, and mail stores
  3. 3. Review the Zimbra Upgrade Guide at https://wiki.zimbra.com for your specific upgrade path
  4. 4. Download Zimbra Collaboration Suite version 10.1.4 or later from the official Zimbra repository
  5. 5. Stop Zimbra services before upgrade: su - zimbra -c 'zmcontrol stop'
  6. 6. Run the Zimbra installer for the new version: ./install.sh -s (or appropriate installer for your platform)
  7. 7. Follow the on-screen prompts to complete the upgrade
  8. 8. Start Zimbra services after upgrade: su - zimbra -c 'zmcontrol start'
Caveat Zimbra major version upgrades may introduce configuration or feature changes - review release notes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zimbra Collaboration Suite Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32354 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32354 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data