dbcve.org
CollaborationApplication · Zimbra

CVE-2023-45206

MEDIUM · 6.1 CVSS v3.1 Published 2024-02-13
Fix available
A fix is available. Upgrade to 10.0.5 or later.
See remediation →
68/100
Remediation priority · Elevated
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
An issue was discovered in Zimbra Collaboration (ZCS) 8.8.15, 9.0, and 10.0. Through the help document endpoint in webmail, an attacker can inject JavaScript or HTML code that leads to cross-site scripting (XSS). (Adding an adequate message to avoid malicious code will mitigate this issue.)

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 · moderate confidence

A cross-site scripting (XSS) vulnerability exists in Zimbra Collaboration (ZCS) versions 8.8.15, 9.0, and 10.0. The help document endpoint in webmail fails to properly sanitize user-supplied input, allowing attackers to inject malicious JavaScript or HTML code that executes in the context of other users' browsers.

MitigationImplement proper input validation and output encoding on the help document endpoint. The vendor notes that adding an adequate message to avoid malicious code will mitigate this issue, suggesting input sanitization or a message filtering mechanism.

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
CollaborationApplication
Affected:>= 10.0.0, < 10.0.5= 8.8.15= 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 Collaboration installation
    Check for Zimbra installation by searching for common Zimbra directories (such as /opt/zimbra) or by running 'zmcontrol -v' if the zmcontrol command is available.
    Affected if Zimbra Collaboration software is not present on the system.
  2. Determine installed ZCS version
    Run 'zmcontrol -v' or check the Zimbra version file typically found in /opt/zimbra/.version to obtain the exact installed version number.
    Affected if The installed version matches one of the affected ranges: 8.8.15, 9.0.0, or 10.0.0 through 10.0.4.
  3. Verify webmail component is enabled
    Check if the Zimbra webmail service (mailboxd) is running by executing 'zmcontrol status' and confirming the 'mailboxd' service is listed as running.
    Affected if The webmail component is not enabled or not running.
  4. Confirm help document endpoint is accessible
    Attempt to access the help document endpoint in webmail (typically at /zimbra/help/ or similar paths under the web server root) via HTTP request to determine if the endpoint responds.
    Affected if The help document endpoint is not accessible or returns an error.

A system is affected if it runs Zimbra Collaboration versions 8.8.15, 9.0.0, or 10.0.0 through 10.0.4 with the webmail help document endpoint accessible.

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.0.5 or later
Fixed in 10.0.5
Interim mitigation

Implement proper input validation and output encoding on the help document endpoint. The vendor notes that adding an adequate message to avoid malicious code will mitigate this issue, suggesting input sanitization or a message filtering mechanism.

Recommended fix Moderate confidence

10.0.5 (for 10.0.x branch); Contact vendor for 8.8.15/9.0.0 patch or upgrade path

  1. Verify the current Zimbra Collaboration version by checking the administration console or running 'zmcontrol -v'
  2. Schedule a maintenance window for the upgrade
  3. Backup the current Zimbra configuration and mail stores
  4. For ZCS 10.0.x: Upgrade to version 10.0.5 or later
  5. For ZCS 8.8.15 and 9.0.0: Contact Zimbra support for patch availability or consider upgrading to a supported 10.0.x release
  6. After upgrade, verify the help document endpoint is properly sanitized by testing with a benign script payload
  7. Clear browser cache and test webmail login functionality
Caveat Review Zimbra 10.0.5 release notes for any breaking changes before upgrading

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

Fix this in Collaboration Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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