CVE-2019-11825
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 · uneditedCross-site scripting (XSS) vulnerability in Event Editor in Synology Calendar before 2.3.0-0615 allows remote attackers to inject arbitrary web script or HTML via the title parameter.
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 confidenceStored cross-site scripting (XSS) vulnerability in Synology Calendar's Event Editor allows remote attackers to inject malicious JavaScript or HTML through the title parameter. This is a classic input validation failure where user-supplied data in the event title field is not properly sanitized before being stored and rendered to other users viewing the calendar event.
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.3.0-0615CVSS 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.
-
Confirm Synology Calendar is installedAccess the Synology DiskStation Manager (DSM) web interface, then navigate to Package Center and look for Synology Calendar in the installed package list, or check for the calendar web portal at /calendar/Affected if Synology Calendar is not listed in installed packages or the calendar portal is not accessible
-
Identify the installed versionIn DSM Package Center, click on Synology Calendar and view the version number displayed in the package details pane, or access the calendar portal and check the About/Help section for version informationAffected if The version number is lower than 2.3.0-0615
-
Verify the Event Editor is accessibleLog into the Synology Calendar web portal and attempt to create a new event or edit an existing event to confirm the Event Editor interface loadsAffected if The Event Editor is accessible and the calendar is used by multiple users (stored XSS affects users who view the crafted event title)
-
Check for existing events with unsanitized titlesReview calendar events in the web interface and inspect event titles for any suspicious characters or script tags that may indicate prior exploitationAffected if Events contain unsanitized HTML or script tags in their titles visible to other users
A user is affected if Synology Calendar is installed with a version lower than 2.3.0-0615 and the calendar is accessible to multiple users who can create or view events through the Event Editor.
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.
From vendor data2.3.0-0615
Update Synology Calendar to version 2.3.0-0615 or later which patches the input validation in the Event Editor to properly sanitize the title parameter.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11825 — 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-2019-11825 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