dbcve.org
Zimbra Collaboration SuiteApplication · Synacor

CVE-2025-25065

MEDIUM · 5.3 CVSS v3.1 Published 2025-02-03
Fix available
A fix is available. Upgrade to 9.0.0 / 10.0.12 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
SSRF vulnerability in the RSS feed parser in Zimbra Collaboration 9.0.0 before Patch 43, 10.0.x before 10.0.12, and 10.1.x before 10.1.4 allows unauthorized redirection to internal network endpoints.

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

This is a Server-Side Request Forgery (SSRF) vulnerability in Zimbra Collaboration's RSS feed parser. The vulnerability allows unauthenticated attackers to trick the server into making requests to internal network endpoints, potentially enabling reconnaissance of internal services, cloud metadata endpoints, or other internal resources.

MitigationApply the relevant patch (Patch 43 for 9.0.0, 10.0.12 for 10.0.x, or 10.1.4 for 10.1.x) to address the SSRF in the RSS feed parser. Additionally, network segmentation and restricting outbound access from the Zimbra server can limit the impact of SSRF attacks.

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.0.0, < 10.0.12>= 10.1.0, < 10.1.4= 9.0.0

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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/readme' to determine the installed Zimbra Collaboration Suite version
    Affected if The version falls within < 9.0.0, = 9.0.0, >= 10.0.0 to < 10.0.12, or >= 10.1.0 to < 10.1.4
  2. Locate the RSS feed parser module
    Search for RSS-related files in the Zimbra installation directory, typically under /opt/zimbra/ - look for files containing 'rss' in the name within the mail service components
    Affected if The RSS parser module exists in the Zimbra installation and is accessible to the web interface
  3. Verify RSS feed functionality is exposed
    Check the Zimbra web interface configuration for RSS feed import features, typically accessible via the mail preferences or filters section
    Affected if Users can configure or import RSS feeds through the Zimbra web interface without administrative privileges
  4. Check outbound network access from Zimbra server
    Review firewall rules or run 'iptables -L' or 'ufw status' to determine if the Zimbra server can make outbound HTTP/HTTPS requests to internal network addresses
    Affected if The Zimbra server has outbound network access allowing it to reach internal services, cloud metadata endpoints (such as 169.254.169.254), or other internal resources

The server is affected if it runs a Zimbra version in the ranges < 9.0.0, = 9.0.0, >= 10.0.0 to < 10.0.12, or >= 10.1.0 to < 10.1.4 AND the RSS feed parser feature is accessible to users.

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 9.0.0 / 10.0.12 / 10.1.4 or later
Fixed in 9.0.010.0.1210.1.4
Interim mitigation

Apply the relevant patch (Patch 43 for 9.0.0, 10.0.12 for 10.0.x, or 10.1.4 for 10.1.x) to address the SSRF in the RSS feed parser. Additionally, network segmentation and restricting outbound access from the Zimbra server can limit the impact of SSRF attacks.

Recommended fix High confidence

Zimbra 9.0.0 with Patch 43; Zimbra 10.0.12 or later; Zimbra 10.1.4 or later

  1. For Zimbra 9.0.0: Apply Patch 43 to address the SSRF vulnerability in the RSS feed parser
  2. For Zimbra 10.0.x (versions < 10.0.12): Upgrade to version 10.0.12 or later
  3. For Zimbra 10.1.x (versions < 10.1.4): Upgrade to version 10.1.4 or later
  4. After applying the patch or upgrade, verify the RSS feed parser configuration to ensure external feed sources are properly restricted
Caveat Review Zimbra release notes for Patch 43 or target versions to check for any configuration or feature changes that may affect your deployment

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

Fix this in Zimbra Collaboration Suite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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