basicsecurity.net
Proof, not just disclosure.
Threats / Synacor / CVE-2022-27926
CVE-2022-27926 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

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-033EPSS 0.17252 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported 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).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.17252 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Synacor, Zimbra Collaboration Suite (ZCS). Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
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; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 9 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by mitre (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.