CVE-2025-48700
Synacor Zimbra Collaboration Suite (ZCS) Cross-site Scripting Vulnerability
An issue was discovered in Zimbra Collaboration (ZCS) 8.8.15 and 9.0 and 10.0 and 10.1. A Cross-Site Scripting (XSS) vulnerability in the Zimbra Classic UI allows attackers to execute arbitrary JavaScript within the user's session, potentially leading to unauthorized access to sensitive information. This issue arises from insufficient sanitization of HTML content, specifically involving crafted tag structures and attribute values that include an @import directive and other script injection vectors. The vulnerability is triggered when a user views a crafted e-mail message in the Classic UI, requiring no additional user interaction.
Published Updated Sources: NVD, Synacor (CNA), CISA, FIRST EPSS, GitHub, GitHub Security Advisory
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Confirmed
CISA KEV, listed Apr 20, 2026
EPSS
2%
ahead of 76% of scored CVEs
CVSS base
6.1
medium
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script all four kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component
Remediation
The vendor's own words where we have them.
Upgrade Zimbra Collaboration Suite (ZCS) to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
CISA required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Federal deadline Apr 23, 2026 — passed 124 days ago
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Treat as emergency remediation because CISA KEV status is present.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| Synacor | Zimbra Collaboration Suite (ZCS) | — | Vulnerable |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Availability
None
Confidentiality
Low
Integrity
Low
Scope
Changed
Attack Complexity
Low
Attack Vector
Network
Privileges Req
None
User Interaction
Required
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 6.1 | CVSS 3.1 | medium | 2.8 | 2.7 | CNA, GHSA |
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Weakness & attack patterns
- CWE-79Cross-site Scripting
Inferred from the weakness class — not observed against this CVE.
CISA KEV details
CISA lists a CVE here once it has evidence of exploitation against real targets.
Listed
Apr 20, 2026
Federal deadline
Apr 23, 2026
passed 124 days ago
Ransomware use
Unknown
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Repositories
2
1 of the 2 sampled are weaponized
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Prioritize edge telemetry for network-reachable Zimbra Collaboration Suite (ZCS).
- Monitor for scanner or exploit-pattern traffic after 2 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added · CVSS 3.1 6.1 (AV:N)
Jun 17, 2026 · NVD
Added to CISA KEV catalog
Apr 20, 2026 · CISA
- 2025
Initial · CVE published
Jun 23, 2025 · NVD
Added · GHSA-wmq6-ffv7-gqwf published (medium)
Jun 23, 2025 · GitHub Security Advisory
References
6 on the record
- wiki.zimbra.com/wiki/Security_Center
Release Notes
- wiki.zimbra.com/wiki/Zimbra_Responsible_Disclosure_Policy
Product
- wiki.zimbra.com/wiki/Zimbra_Security_Advisories
Vendor Advisory
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-48700
US Government Resource
- nvd.nist.gov/vuln/detail/CVE-2025-48700
NVD, Vendor Advisory
- github.com/advisories/GHSA-wmq6-ffv7-gqwf
Exploit, Third Party Advisory
Elsewhere on this site
- Synacorevery CVE for this vendor
- April 2026what else CISA listed
- Injectionsame class
- CWE-79other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2025-48700 is Synacor Zimbra Collaboration Suite (ZCS) Cross-site Scripting Vulnerability, a medium vulnerability affecting Zimbra Collaboration Suite (ZCS) from Synacor. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 2 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 6.1 describes technical severity, while EPSS 2% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.