CVE-2024-45514 json
An issue was discovered in Zimbra Collaboration (ZCS) through v10.1.
published last yr. modified 4mo ago also EUVD-2024-41684
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 52%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- synacor zimbra_collaboration_suite 8.8.15, 10.0.9
Is CVE-2024-45514 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.67% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-11).
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
-
wiki.zimbra.com
/wiki/Zimbra_Releases/8.8.15/P46#Security_Fixes
release-notes
Sources
- CVE List CVE-2024-45514
- NVD CVE-2024-45514
Fencer Intel 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.