CVE-2022-41351
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 · uneditedIn Zimbra Collaboration Suite (ZCS) 8.8.15, at the URL /h/calendar, one can trigger XSS by adding JavaScript code to the view parameter and changing the value of the uncheck parameter to a string (instead of default value of 10).
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 confidenceThis is a reflected XSS vulnerability in Zimbra Collaboration Suite 8.8.15 at the /h/calendar endpoint. Attackers can inject arbitrary JavaScript code through the 'view' parameter by manipulating the 'uncheck' parameter from its default numeric value (10) to a string value, causing the application to fail to sanitize the view parameter output.
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= 8.8.15CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Zimbra version is 8.8.15Run 'zmcontrol -v' or check the Zimbra admin console for the installed version. Compare to the affected range = 8.8.15Affected if The installed Zimbra Collaboration Suite version is exactly 8.8.15
-
Verify /h/calendar endpoint is exposedAttempt to access the /h/calendar endpoint via HTTP/HTTPS (e.g., https://yourserver/h/calendar). Check if the endpoint returns a valid response.Affected if The /h/calendar endpoint is accessible and returns a valid page
-
Test for reflected XSS in the view parameterSend a crafted request to /h/calendar with a test payload in the 'view' parameter (e.g., view=<script>alert(1)</script>). Inspect the response to see if the payload is reflected without encoding.Affected if The 'view' parameter value is reflected in the response without proper HTML encoding
-
Check uncheck parameter behaviorSend a request with 'uncheck' set to a string value (e.g., uncheck=test) instead of the default numeric value (10). Observe if this triggers unsanitized output of the view parameter.Affected if Using a non-numeric value for 'uncheck' causes the view parameter to be rendered without sanitization
You are affected if running Zimbra 8.8.15 with the /h/calendar endpoint exposed and the view parameter reflects input without encoding when the uncheck parameter is manipulated from its default numeric value.
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 · scopedImplement proper input validation and output encoding on the 'view' and 'uncheck' parameters at the /h/calendar endpoint to neutralize malicious script payloads before rendering.
ZCS 8.8.15 Patch 23 or later (check wiki.zimbra.com for latest security patch)
- 1. Identify the current ZCS 8.8.15 patch level by checking the /opt/zimbra/.patching_history file or running 'zmcontrol -v'
- 2. Access the Zimbra support portal or wiki.zimbra.com to obtain the appropriate patch for version 8.8.15
- 3. Download the patch file (Patch 23 or later as indicated in Zimbra security advisories)
- 4. Run the patch installation as the zimbra user: './install.sh --patch-license' or as documented in the patch release notes
- 5. Verify the patch applied successfully by checking the patch level again
- 6. Test the /h/calendar endpoint to confirm the XSS vulnerability is mitigated (ensure view and uncheck parameters are properly sanitized)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41351 — 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-2022-41351 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