dbcve.org
CollaborationApplication · Zimbra

CVE-2023-43102

MEDIUM · 6.1 CVSS v3.1 Published 2023-12-07
Fix available
A fix is available. Upgrade to 8.8.15 / 10.0.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Patch available

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) before 10.0.4. An XSS issue can be exploited to access the mailbox of an authenticated user. This is also fixed in 8.8.15 Patch 43 and 9.0.0 Patch 36.

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
How this class of weakness works · CWE-79

Untrusted input is placed into a web page without being neutralised, so an attacker's markup or script executes in another user's browser. That can hijack sessions, capture keystrokes, or silently perform actions as the victim. Fixing it properly means context-aware output encoding everywhere data meets HTML, backed by a content-security policy as a second line of defence.

General guidance for the cross-site scripting (xss) class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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:< 8.8.15>= 10.0.0, < 10.0.4= 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

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 8.8.15 / 10.0.4 or later
Fixed in 8.8.1510.0.4
Vendor patch wiki.zimbra.com →
Recommended fix High confidence

10.0.4 (for 10.x); 8.8.15 Patch 43 (for 8.8.x); 9.0.0 Patch 36 (for 9.0.0)

  1. 1. Identify the current Zimbra Collaboration version by running: zmcontrol -v or checking the Admin Console
  2. 2. Based on the current major version, upgrade to the appropriate fixed release:
  3. - For ZCS 10.x: Upgrade to version 10.0.4
  4. - For ZCS 8.8.x: Apply Patch 43 (8.8.15 Patch 43)
  5. - For ZCS 9.0.0: Apply Patch 36 (9.0.0 Patch 36)
  6. 3. Obtain the patch/upgrade from the official Zimbra repository or Zimbra's support portal
  7. 4. Apply the upgrade or patch following Zimbra's standard upgrade procedures
  8. 5. Restart Zimbra services after the upgrade: zmcontrol restart
Caveat Standard Zimbra upgrade risks apply - ensure backups are in place and test in a non-production environment before applying to production

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $900. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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