CVE-2018-14425
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 · uneditedThere is a Persistent XSS vulnerability in the briefcase component of Synacor Zimbra Collaboration Suite (ZCS) Zimbra Web Client (ZWC) 8.8.8 before 8.8.8 Patch 7 and 8.8.9 before 8.8.9 Patch 1.
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 confidenceA persistent Cross-Site Scripting (XSS) vulnerability exists in the briefcase (file storage) component of Zimbra Web Client. The vulnerability allows injection of malicious scripts that are stored on the server and executed when other users view the affected briefcase content. Affected versions are ZCS 8.8.8 before Patch 7 and 8.8.9 before Patch 1.
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< 8.8.8= 8.8.8= 8.8.9CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Check Zimbra Collaboration Suite versionRun 'zmcontrol -v' or 'zmmsgcfg --version' from the command line as the zimbra user, or check the admin console for the server version.Affected if The version displayed is < 8.8.8, equals 8.8.8, or equals 8.8.9 (without respective patches applied).
-
Verify patch status on 8.8.8Run 'zmcontrol -v' and look for 'Patch 7' or higher in the version string, or check /opt/zimbra/versions.json for patch level.Affected if Running 8.8.8 without Patch 7 or higher installed.
-
Verify patch status on 8.8.9Run 'zmcontrol -v' and look for 'Patch 1' or higher in the version string, or check /opt/zimbra/versions.json for patch level.Affected if Running 8.8.9 without Patch 1 or higher installed.
-
Confirm briefcase feature is accessibleLog into Zimbra Web Client as a regular user and check if the Briefcase module appears in the navigation, or query the mailbox database for briefcase items: 'select count(*) from mailbox_item where mailbox_id in (select id from mailbox) and item_type = 2;'Affected if Briefcase feature is enabled and users have access to upload or view briefcase content.
You are affected if your ZCS version is < 8.8.8, equals 8.8.8 without Patch 7, or equals 8.8.9 without Patch 1, AND the Briefcase feature is accessible to users in your environment.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data8.8.8
Apply the vendor-supplied patches: ZCS 8.8.8 Patch 7 or 8.8.9 Patch 1, which address the input sanitization flaw in the briefcase component.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14425 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-14425 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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