CVE-2016-3407
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 104222, 104910, 105071, and 105175.
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 confidenceMultiple cross-site scripting (XSS) vulnerabilities exist in Zimbra Collaboration versions prior to 8.7.0. These allow remote unauthenticated attackers to inject arbitrary JavaScript or HTML through unspecified input vectors (tracked as bugs 104222, 104910, 105071, and 105175), potentially enabling session hijacking, credential theft, or defacement of web interfaces.
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.
-
Verify Zimbra Collaboration is installedCheck for the presence of the Zimbra installation directory at /opt/zimbra or run 'which zmcontrol' to locate the Zimbra control binaryAffected if Zimbra is not found on the system, the system is not affected by this CVE
-
Determine the installed Zimbra versionRun 'zmcontrol -v' as the zimbra user or check /opt/zimbra/.gitdescribe or /opt/zimbra/version.txt to retrieve the exact version numberAffected if The version cannot be determined or the command fails, manual verification is required
-
Compare version against affected rangeReview the version output and determine if it is 8.6.0 or earlier (for example: 8.6.0, 8.5.1, 8.0.x, 7.x)Affected if The installed version is 8.6.0 or any earlier version (8.x before 8.7.0, or 7.x releases), the system is vulnerable to CVE-2016-3407
-
Confirm the Zimbra web service is enabledRun 'zmcontrol status' as the zimbra user to check if the mailbox, mta, or web services are runningAffected if The web interface (mailboxd/httpd) is not running, exploitation is not possible in that state but the underlying vulnerability still exists in the software
The environment is affected if Zimbra Collaboration Suite version 8.6.0 or earlier is installed, regardless of whether the web service is currently running.
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 Zimbra Collaboration to version 8.7.0 or later to address all four XSS vulnerabilities. If immediate upgrade is not feasible, implement input validation and output encoding on all user-facing interfaces as a temporary mitigation.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3407 — 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-3407 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