Skip to main content
VulnerabilityPublished

CVE-2026-66912: Synacor Zimbra Collaboration · Cross-site Scripting

Affects Synacor Zimbra CollaborationSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 10.1.21 when convenient.

Data as of 29 Oct 2026, 15:38 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (CERT-PL)CVSS 4.05.3
Patch
Available – fixed in 10.1.21
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade Synacor Zimbra Collaboration to 10.1.21.

Affected software

ProductAffectedFixed in
SynacorZimbra CollaborationAffected
  • <10.1.21
Fixed in
  • 10.1.21

Description

Zimbra is vulnerable to Stored Cross-Site Scripting (XSS) via the From email header during HTML reply composition in Classic UI. Due to insufficient sanitization of the From header value, a remote attacker can send a crafted email containing a malicious From header with an embedded JavaScript payload. When the victim opens the message in Classic UI and clicks Reply while composing in HTML mode with reply headers disabled, the unsanitized From header content is rendered as HTML and the JavaScript payload executes in the victim's browser, potentially allowing the attacker to steal session information or perform actions on behalf of the victim. This issue was fixed in version 10.1.21

References

Community reviews

Loading reviews…