dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 11 Mar 2022. Known ransomware use
Zimbra Collaboration SuiteApplication · Synacor

CVE-2022-24682

MEDIUM · 6.1 CVSS v3.1 Published 2022-02-09
Fix available
A fix is available. Upgrade to 8.8.15 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware Public exploit Remotely reachable No privileges

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 · unedited
An issue was discovered in the Calendar feature in Zimbra Collaboration Suite 8.8.x before 8.8.15 patch 30 (update 1), as exploited in the wild starting in December 2021. An attacker could place HTML containing executable JavaScript inside element attributes. This markup becomes unescaped, causing arbitrary markup to be injected into the document.

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 confidence

A cross-site scripting (XSS) vulnerability in Zimbra Collaboration Suite's Calendar feature allows attackers to inject HTML containing executable JavaScript into element attributes. User-supplied markup is not properly escaped, enabling arbitrary script execution when the calendar content is rendered.

MitigationApply Zimbra 8.8.15 patch 30 (update 1) or later to remediate the input validation flaw in the Calendar feature.

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
Zimbra Collaboration SuiteApplication
Affected:>= 8.8.0, < 8.8.15= 8.8.15

CVSS 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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Zimbra Collaboration Suite version
    Run 'zmcontrol -v' or 'zmversion' command as the zimbra user to retrieve the installed Zimbra version
    Affected if Version is 8.8.0 through 8.8.14, or exactly 8.8.15 (unpatched)
  2. Check Zimbra patch level
    Run 'zmcontrol -v' or check the /opt/zimbra/.install_history file to see if patch 30 or later is applied
    Affected if Patch level is below 30 on version 8.8.15, or no patch information is shown on versions 8.8.0-8.8.14
  3. Verify Calendar module is accessible
    Log into Zimbra Web Client and navigate to the Calendar section, or check via: 'zmprov getAccount [email protected] zimbraFeatureCalendarEnabled'
    Affected if Calendar feature is enabled for any user account (required for the XSS to be exploitable)
  4. Check for recent calendar invite modifications
    Review Zimbra mailbox logs (/opt/zimbra/log/mailbox.log) for unusual calendar appointment entries or inspect the calendar.sqlite database for unexpected attributes
    Affected if Suspicious HTML or script tags found in calendar event attributes that were not created by legitimate users

A Zimbra server is affected if it runs version 8.8.0 through 8.8.14 (unpatched) or version 8.8.15 without patch 30, and has the Calendar feature enabled allowing stored XSS to execute via malicious calendar invites.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 8.8.15 or later
Fixed in 8.8.15
Interim mitigation

Apply Zimbra 8.8.15 patch 30 (update 1) or later to remediate the input validation flaw in the Calendar feature.

Recommended fix High confidence

Zimbra Collaboration Suite 8.8.15 Patch 30 (Update 1) or later

  1. 1. Identify the current Zimbra Collaboration Suite version and patch level by running: zmcontrol -v or checking the /opt/zimbra/.log directory
  2. 2. Verify if the current installation is vulnerable: affected versions are 8.8.0 through 8.8.15 patch 29 (or patch 30 and below)
  3. 3. Download Zimbra Collaboration Suite 8.8.15 Patch 30 (also referred to as Update 1) from the official Zimbra package repository or support portal
  4. 4. Apply the patch following Zimbra's standard patching procedure: typically run as the zimbra user: apt-get update && apt-get install zimbra-patch or similar based on OS
  5. 5. Restart Zimbra services to ensure the patch takes effect: zmcontrol restart
  6. 6. Verify the patch was applied successfully: zmcontrol -v should show version 8.8.15 patch 30 or higher
  7. 7. Test the Calendar feature to confirm the XSS vulnerability is remediated by attempting to inject HTML/JavaScript in calendar event attributes
Caveat Review Zimbra release notes for patch 30 to check for any configuration or compatibility considerations before applying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zimbra Collaboration Suite Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24682 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-24682 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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