Threats / Synacor / CVE-2020-7796
CVE-2020-7796
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Synacor Zimbra Collaboration Suite vulnerability
Synacor Zimbra Collaboration Suite contains a server-side request forgery vulnerability when the WebEx zimlet is installed and zimlet JSP is enabled, allowing remote exploitation.
Verdict
Today item — known-exploited.
A server-side request forgery flaw in Zimbra Collaboration Suite enables attackers to make unauthorized requests from the affected server to internal or external systems, potentially bypassing network controls and accessing restricted resources.
CISA KEV Yes · 2026-02-174EPSS 0.84418 (verify live)5CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3Exploit Public PoC / detection · nuclei template12
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
593 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 2026-02-17).
Probability (EPSS)
EPSS 0.84418 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Synacor, Zimbra Collaboration Suite. 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-918 Server-Side Request Forgery (SSRF).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: yes · Technical Impact: totalCISA'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 2191 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 request targeting the WebEx zimlet JSP endpoint to trigger server-side request forgery.
Business
Attackers gain the ability to probe internal network topology and access services restricted by firewall rules.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I leverage the SSRF to access internal metadata services or cloud provider credentials exposed on the server.
Business
Compromise of authentication credentials or sensitive configuration data stored on or accessible from the mail server.
3
Lateral reach — past segmentation narrative 3
Attacker
I use the server as a proxy to attack other internal systems or services that trust the mail server's network position.
Business
Lateral movement into backend infrastructure, potentially compromising databases, file servers, or other critical systems.
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