CVE-2024-45510
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceZimbra Webmail Modern UI suffers from a stored XSS vulnerability where malicious script injected into email message fields persists and executes when victims add the attacker to their contacts and subsequently view their contact list. The lack of proper input sanitization and output encoding allows the attacker to perform actions like arbitrary mail sending, mailbox exfiltration, and profile modifications.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 9.0.0>= 10.0.0, < 10.0.9= 9.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Zimbra Collaboration Suite versionRun 'zmcontrol -v' from the Zimbra server command line, check the administration console version display, or inspect version files in /opt/zimbra/ to determine the installed ZCS versionAffected if Version is less than 9.0.0, equals 9.0.0, or is 10.0.0 through 10.0.8 (versions below 10.0.9)
-
Confirm Modern UI is activeCheck the Zimbra web client configuration or user preferences to verify if the Modern UI (also known as the new experience) is enabled for the mailboxAffected if Modern UI is enabled and the installed version falls within the affected ranges
-
Review contact data for injected contentExport contacts from the Zimbra web interface or query the mailbox database directly to inspect contact fields (name, email, address) for unsanitized script tags or HTMLAffected if Contact entries contain raw script tags, javascript: URIs, or event handler attributes that indicate stored XSS payloads
A user is affected if they are running a Zimbra version in the range (< 9.0.0, 9.0.0, or 10.0.0-10.0.8) with Modern UI enabled and have contacts or have received emails containing unencoded malicious script content.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.0.010.0.9
Implement proper input sanitization and output encoding for all user-supplied data in email fields and contact management functions to prevent script execution.
Zimbra Collaboration Suite 10.0.9 or later
- 1. Backup your Zimbra Collaboration Suite installation and database before proceeding with any upgrade.
- 2. Download the latest Zimbra Collaboration Suite version 10.0.9 or later from the official Zimbra repository.
- 3. Stop all Zimbra services using: zmcontrol stop
- 4. Install the updated Zimbra packages for version 10.0.9 or later.
- 5. Start Zimbra services using: zmcontrol start
- 6. Verify the upgrade was successful by logging into the Zimbra Modern UI webmail.
- 7. Test that the contact functionality works properly after the upgrade.
- 8. Clear browser cache to ensure no cached vulnerable code remains.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45510 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-45510 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data