CVE-2024-45518: Zimbra Collaboration · Server-Side Request Forgery (SSRF)
Source CVE Database V5
Not known to be exploited · 20% EPSS · CVSS 7.5 High · fixed in 10.1.1 : patch affected systems soon.
Data as of 26 Oct 2026, 12:54 UTC
- EPSS
- 20.7% chance of exploitation in 30 days – higher than 97% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.1.1, 10.0.9
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 22 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
- Immediately apply the latest patches provided by Zimbra for versions 8.8.15, 9.0.0, 10.0.x, and 10.1.x to remediate the vulnerability.
- Review and tighten domain whitelisting configurations to ensure only trusted domains are allowed for internal requests.
- Implement strict input validation and sanitization on all user-supplied data that can influence server-side requests.
- Conduct a thorough security assessment of internal services accessible via the mail server to identify and remediate command injection or other vulnerabilities.
- Monitor logs for unusual internal HTTP requests originating from the mail server that could indicate SSRF attempts.
- Harden the Zimbra server environment by applying least privilege principles and network segmentation to limit the impact of potential RCE.
- Regularly scan for and remediate XSS vulnerabilities to reduce the risk of chained attacks.
- Educate administrators on secure configuration best practices for Zimbra and internal services.
- Consider deploying Web Application Firewalls (WAFs) with rules to detect and block SSRF patterns targeting internal resources.
Description
An issue was discovered in Zimbra Collaboration (ZCS) 10.1.x before 10.1.1, 10.0.x before 10.0.9, 9.0.0 before Patch 41, and 8.8.15 before Patch 46. It allows authenticated users to exploit Server-Side Request Forgery (SSRF) due to improper input sanitization and misconfigured domain whitelisting. This issue permits unauthorized HTTP requests to be sent to internal services, which can lead to Remote Code Execution (RCE) by chaining Command Injection within the internal service. When combined with existing XSS vulnerabilities, this SSRF issue can further facilitate Remote Code Execution (RCE).
References
- wiki.zimbra.com/wiki/Zimbra_Security_Advisories (opens in a new tab)
- wiki.zimbra.com/wiki/Security_Center (opens in a new tab)
- wiki.zimbra.com/wiki/Zimbra_Responsible_Disclosure_Policy (opens in a new tab)
- wiki.zimbra.com/wiki/Zimbra_Releases/10.1.1 (opens in a new tab)
- wiki.zimbra.com/wiki/Zimbra_Releases/10.0.9 (opens in a new tab)
- wiki.zimbra.com/wiki/Zimbra_Releases/9.0.0/P41 (opens in a new tab)
- wiki.zimbra.com/wiki/Zimbra_Releases/8.8.15/P46 (opens in a new tab)