CVE-2022-22682
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 · uneditedImproper neutralization of input during web page generation ('Cross-site Scripting') vulnerability in Event Management in Synology Calendar before 2.4.5-10930 allows remote authenticated users to inject arbitrary web script or HTML via unspecified vectors.
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 · moderate confidenceA stored Cross-site Scripting (XSS) vulnerability exists in the Event Management feature of Synology Calendar versions prior to 2.4.5-10930. Authenticated users can inject malicious web scripts or HTML into event data, which is then executed when other users view the affected events.
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< 2.4.5-10930CVSS 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.
-
Verify Synology Calendar is installedLog into the Synology NAS admin interface, open Package Center, and look for Synology Calendar in the installed package list. Alternatively, run: ls -la /var/packages/ | grep -i calendarAffected if Synology Calendar package is not found in the installed packages
-
Determine installed Synology Calendar versionIn Package Center, click on Synology Calendar and view the version information. Alternatively, run: cat /var/packages/SynologyCalendar/info.json 2>/dev/null || cat /var/packages/SynologyCalendar/INFOAffected if Version is displayed as lower than 2.4.5-10930 or cannot be determined to be 2.4.5-10930 or higher
-
Confirm Calendar service is accessible to usersLog into Synology Calendar as an authenticated user and verify the Event Management feature is accessible. Check if standard users can create or edit calendar events.Affected if The Calendar application is running and users can access the Event Management feature to create or edit events
-
Identify user access levels in CalendarIn Synology Calendar settings or DSM user management, review which users or groups have permission to create or edit calendar events.Affected if There are authenticated users (beyond administrators) who have permission to create or modify calendar events
You are affected if Synology Calendar is installed with a version prior to 2.4.5-10930 and the Calendar service with Event Management is accessible to authenticated users who can create or edit events.
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 · scoped2.4.5-10930
Update Synology Calendar to version 2.4.5-10930 or later, which contains the fix for proper input sanitization in the Event Management component.
Synology Calendar version 2.4.5-10930 or later
- Log into Synology DiskStation Manager (DSM)
- Open Package Center
- Locate Synology Calendar in the package list
- Click on the Synology Calendar package and select Update
- Ensure the update installs version 2.4.5-10930 or later
- Verify the update was successful by checking the installed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22682 — 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-22682 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