Skip to main content
VulnerabilityPublished

CVE-2024-45514: Zimbra Collaboration · Cross-site Scripting

Source CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium · fixed in 10.2 : update affected systems when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 10.2
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

To mitigate CVE-2024-45514, organizations should implement the following specific measures: 1) Apply strict input validation and output encoding on the 'packages' parameter within Zimbra Webmail endpoints to prevent injection of malicious scripts. 2) Employ Web Application Firewalls (WAFs) with custom rules to detect and block encoded payloads targeting the vulnerable parameter. 3) Educate users on the risks of clicking suspicious links and implement email filtering to reduce phishing attempts that could deliver exploit URLs. 4) Monitor webmail access logs for unusual patterns or repeated attempts to access the vulnerable endpoint with suspicious parameters. 5) Restrict privileges where possible to minimize the impact of compromised accounts. 6) Stay alert for official patches or updates from Zimbra and apply them promptly once available. 7) Consider deploying Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in the webmail interface. 8) Conduct regular security assessments and penetration testing focused on webmail components to identify and remediate similar vulnerabilities proactively.

Description

An issue was discovered in Zimbra Collaboration (ZCS) through v10.1. A Cross-Site Scripting (XSS) vulnerability exists in one of the endpoints of Zimbra Webmail due to insufficient sanitization of the packages parameter. Attackers can bypass the existing checks by using encoded characters, allowing the injection and execution of arbitrary JavaScript within a victim's session.

References

Community reviews

Loading reviews…