CVE-2016-3412
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 · uneditedMultiple cross-site scripting (XSS) vulnerabilities in Zimbra Collaboration before 8.7.0 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors, aka bugs 103997, 104413, 104414, 104777, and 104791.
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 confidenceMultiple cross-site scripting (XSS) vulnerabilities exist in Zimbra Collaboration versions prior to 8.7.0, allowing remote attackers to inject arbitrary JavaScript or HTML through unspecified vectors in the web application interface.
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.6.0CVSS 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.
-
Confirm Zimbra Collaboration is installedLook for Zimbra installation directories such as /opt/zimbra or /usr/local/zimbra, or check for Zimbra processes running (ps aux | grep -i zimbra)Affected if Zimbra is not found on the system - the CVE does not apply
-
Identify the installed Zimbra versionRun: /opt/zimbra/bin/zmcontrol -v or check /opt/zimbra/.install_history, or examine the Zimbra package manager outputAffected if Version cannot be determined or is not from the 8.x series
-
Compare version to affected rangeIf version is identified, verify whether it is 8.6.0 or lower. Any version prior to 8.7.0 (including 8.5.x, 8.0.x, 7.x) falls within the affected rangeAffected if Installed version is 8.6.0 or lower - system is potentially affected
-
Verify web interface is accessibleConfirm the Zimbra web client (Zimbra Web Client) is enabled and accessible, typically on ports 80, 443, 8080, or 8443. Check /opt/zimbra/conf/nginx.conf or the Zimbra admin console for web service statusAffected if Web interface is disabled and not accessible externally - exploitation is limited to local attack vectors only
System is affected by CVE-2016-3412 if Zimbra Collaboration Suite version 8.6.0 or lower is installed and the web application interface is enabled and accessible.
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 dataUpgrade to Zimbra Collaboration 8.7.0 or later to address all five documented XSS vulnerabilities (bugs 103997, 104413, 104414, 104777, and 104791). If immediate upgrade is not feasible, implement output encoding and input validation on all user-facing fields as a compensating control.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3412 — 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-2016-3412 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