CVE-2024-45510 json
An issue was discovered in Zimbra Collaboration (ZCS) through 10.0.
published 2024-11-20 23 mo ago modified 2026-06-17 4 mo ago also EUVD-2024-41680
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 25%
- public exploits
- 0
- none known
Summary
An issue was discovered in Zimbra Collaboration (ZCS) through 10.0. Zimbra Webmail (Modern UI) is vulnerable to a stored Cross-Site Scripting (XSS) attack due to improper sanitization of user input. This allows an attacker to inject malicious code into specific fields of an e-mail message. When the victim adds the attacker to their contacts, the malicious code is stored and executed when viewing the contact list. This can lead to unauthorized actions such as arbitrary mail sending, mailbox exfiltration, profile picture alteration, and other malicious actions. Proper sanitization and escaping of input fields are necessary to mitigate this vulnerability.
Patch / fix
- synacor zimbra_collaboration_suite 9.0.0, 10.0.9
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 23 mo ago
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
wiki.zimbra.com
/wiki/Security_Center
vendor-advisory
-
wiki.zimbra.com
/wiki/Zimbra_Responsible_Disclosure_Policy
product
-
wiki.zimbra.com
/wiki/Zimbra_Releases/10.1.1#Security_Fixes
release-notes
-
wiki.zimbra.com
/wiki/Zimbra_Releases/10.0.9#Security_Fixes
release-notes
-
wiki.zimbra.com
/wiki/Zimbra_Releases/9.0.0/P41#Security_Fixes
release-notes
Sources
- CVE List CVE-2024-45510
- NVD CVE-2024-45510
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.