Skip to main content
Mallory
MediumCISA KEVExploited in the wildPublic exploit

Stored XSS in Zimbra Collaboration Classic Web Client via ICS files

IdentifiersCVE-2025-27915CWE-79· Improper Neutralization of Input…

CVE-2025-27915 is a stored cross-site scripting vulnerability in Zimbra Collaboration Suite (ZCS) affecting the Classic Web Client. The issue is caused by insufficient sanitization of HTML content embedded in iCalendar (.ICS) files. When a victim views an email message containing a malicious ICS entry, attacker-supplied JavaScript can execute in the context of the victim’s authenticated Zimbra webmail session, including via an ontoggle event inside a <details> tag. Reported affected versions include ZCS 9.0, 10.0, and 10.1, with vulnerable ranges described as 9.0.0 all patches, 10.0.x before 10.0.13, and 10.1.x before 10.1.5. Public reporting also states the flaw was exploited as a zero-day in targeted attacks using weaponized ICS attachments.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows arbitrary JavaScript execution in the victim’s Zimbra session, enabling session hijacking and unauthorized actions on the victim account. Reported post-exploitation outcomes include creation of mail-forwarding rules to attacker-controlled addresses, credential theft, theft of emails, contacts, shared-folder contents, address books, distribution lists, authentication artifacts, and backup tokens, as well as broader data exfiltration through the Zimbra SOAP API. In observed attacks, the vulnerability was used for mailbox takeover and persistent email redirection.

Mitigation

If you can’t patch tonight, do this now.

Until patching is completed, reduce exposure of the Classic Web Client where operationally feasible, monitor for suspicious inbound ICS attachments, and inspect mailboxes for unauthorized filter rules or forwarding settings. Because exploitation is triggered when a user opens an email containing a malicious ICS entry, organizations should also consider filtering or quarantining untrusted calendar attachments, increasing monitoring for anomalous SOAP API activity and outbound exfiltration, and reviewing webmail sessions for signs of injected JavaScript behavior. If mitigations cannot be applied, follow vendor and CISA guidance to discontinue use of affected exposed services where feasible.

Remediation

Patch, then assume compromise.

Upgrade Zimbra Collaboration Suite to a fixed release. The provided content indicates patches were issued on January 27, 2025, and identifies fixed versions as 9.0.0 Patch 44, 10.0.13, and 10.1.5. Other reporting in the content also references ZCS 10.1.9 as containing a fix; however, the more specific versioned patch information provided for the CVE is 9.0.0 Patch 44, 10.0.13, and 10.1.5. Apply the vendor update that strengthens input sanitization for ICS content and verify that exposed Classic Web Client instances are running a non-vulnerable build.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
ZimbraCollaborationapplication
ZimbraZimbra Collaboration Suiteapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence4

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity46

Community discussion across Reddit, Mastodon, and other social sources.