Read the docs
TI-2018-06465 Aliases CVE-2018-8927GHSA-pc82-888m-pq3g

Incorrect authorization in Synology Calendar

Priority LOW 31CWE-863Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
None · High · None
Fix status
Fixed

Attack profile from CVSS 3.0 · NVD. Fix status from CNA. Impact type from CWE-863.

Summary

Improper authorization vulnerability in SYNO.Cal.Event in Calendar before 2.1.2-0511 allows remote authenticated users to create arbitrary events via the (1) cal_id or (2) original_cal_id parameter.

Why it matters now

EPSS 0.00907 60th percentileScored 2026-11-07
Fix Fixed Calendar (Synology): 2.1.2-0511

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
SynologyCalendarbefore 2.1.2-05112.1.2-0511Patch availableCNA
  • Calendar VendorSynology Affected before 2.1.2-0511 Fixed in 2.1.2-0511 Patch available CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:synology:calendar:*:*:*:*:*:*:*:*before 2.1.2-0511VulnerableSynology
  • cpe:2.3:a:synology:calendar:*:*:*:*:*:*:*:* Versions before 2.1.2-0511 Vulnerable ·Synology

Remediation

  • Fix · CNA Calendar (Synology) Fixed in 2.1.2-0511

Timeline

  1. 2026-10-02 Threatist record created from CVE-2018-8927
  2. 2026-10-03 Alias added: GHSA-pc82-888m-pq3g

References

Advisory 1

  • TI-2019-08865 OS command injection in Synology Calendar CVSS 3.1CRITICAL 9.8
  • TI-2022-06947 Cross-site request forgery in Synology Calendar CVSS 3.1HIGH 8.0
  • TI-2021-13806 Hard-coded credentials in Synology Calendar CVSS 3.1HIGH 7.5
  • TI-2018-09547 Path traversal in Synology Calendar CVSS 3.0MEDIUM 6.5
  • TI-2017-11638 Improper access control in Synology Calendar CVSS 3.0MEDIUM 6.5
  • TI-2022-06943 Cross-site scripting in Synology Calendar CVSS 3.1MEDIUM 6.5
See all 10 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences