dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-62763

MEDIUM · 5.0 CVSS v3.1 Published 2025-10-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Zimbra Collaboration (ZCS) before 10.1.12 allows SSRF because of the configuration of the chat proxy.

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

Zimbra Collaboration Suite versions prior to 10.1.12 contain a Server-Side Request Forgery (SSRF) vulnerability in the chat proxy component. The vulnerability stems from improper configuration of the chat proxy, which allows an attacker to induce the server to make arbitrary HTTP requests to internal or external resources.

MitigationUpgrade Zimbra Collaboration Suite to version 10.1.12 or later, or if immediate upgrading is not feasible, reconfigure/disable the chat proxy to restrict request destinations and validate all URLs before forwarding.

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

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
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
None

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

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. Identify Zimbra installation and version
    Run 'zmcontrol -v' or check '/opt/zimbra/.install_history' for version information. Also check '/opt/zimbra/VERSION' if it exists.
    Affected if The installed version is below 10.1.12 (e.g., 10.1.0, 10.0.x, 9.x series)
  2. Determine if chat proxy component is enabled
    Check Zimbra configuration with 'zmprov gcf zimbraChatProxyEnabled' or inspect the localconfig.xml file for the chat proxy setting.
    Affected if The chat proxy is enabled (value returns 'TRUE' or 'true')
  3. Inspect chat proxy URL validation settings
    Check Zimbra's chat proxy configuration files in /opt/zimbra/conf/ or the localconfig.xml for settings related to allowed destinations, URL validation, or proxywhitelist.
    Affected if URL validation is missing, disabled, or allows arbitrary destinations (no whitelist or restrictions configured)
  4. Review proxy configuration for destination restrictions
    Examine /opt/zimbra/jetty/webapps/zimbra/WEB-INF/web.xml or chat-related configuration files in /opt/zimbra/ for proxy destination settings.
    Affected if The proxy configuration lacks destination restrictions or permits internal network addresses

You are affected if running Zimbra version below 10.1.12 with the chat proxy enabled and without proper URL destination restrictions configured.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Zimbra Collaboration Suite to version 10.1.12 or later, or if immediate upgrading is not feasible, reconfigure/disable the chat proxy to restrict request destinations and validate all URLs before forwarding.

Recommended fix Moderate confidence

ZCS 10.1.12 or later (recommended: latest stable 10.x release)

  1. 1. Identify the current ZCS version by running: zmcontrol -v or admin console version info
  2. 2. Create a full backup of the Zimbra mailbox, database, and configuration files before upgrading
  3. 3. Review Zimbra upgrade documentation for your specific version at https://zimbra.com/documentation/
  4. 4. Upgrade Zimbra Collaboration Suite to version 10.1.12 or later (latest stable 10.x release recommended)
  5. 5. After upgrade, verify the chat proxy configuration is correctly set in the admin console
  6. 6. Test that SSRF-prone endpoints in the chat proxy are now properly restricted
  7. 7. Monitor logs for any unusual outbound requests that may indicate exploitation attempts
Caveat Review Zimbra upgrade notes for your current version; major version jumps may require intermediate upgrades and may have configuration migration steps

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62763 — 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-62763 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