Threats / Synacor / CVE-2022-27926
CVE-2022-27926
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Synacor Zimbra Collaboration Suite (ZCS) vulnerability
Synacor Zimbra Collaboration Suite contains a cross-site scripting vulnerability in an endpoint that fails to sanitize URL parameters, enabling injection of malicious scripts.
Verdict
Today item — known-exploited.
A reflected or stored XSS flaw in ZCS allows attackers to inject arbitrary JavaScript through unsanitized endpoint parameters. Active exploitation in the wild combined with high EPSS score indicates immediate risk to deployed instances.
CISA KEV Yes · 2023-04-034EPSS 0.17634 (verify live)5CVSS 6.1 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: partial3Exploit Public PoC / detection · nuclei template12
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
9 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-04-03).
Probability (EPSS)
EPSS 0.17634 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 6.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) · Affected: Synacor, Zimbra Collaboration Suite (ZCS). Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-79 Cross-site Scripting (XSS), CWE-138 CWE-138 — weakness family: Web / client.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: partialCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 348 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious URL containing JavaScript payload in an unsanitized endpoint parameter.
Business
Attackers gain ability to execute arbitrary code in user browsers, compromising session tokens and sensitive data.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I distribute the crafted URL via phishing or watering hole to target ZCS users.
Business
User credentials, emails, and calendar data become accessible to threat actors without detection.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistent access by stealing authentication cookies or injecting backdoor scripts.
Business
Organizational email infrastructure is compromised, enabling lateral movement and data exfiltration campaigns.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05