nextcloud / nextcloud/calendar

Calendar invitation autocomplete ignores global "shareapi" and privacy restrictions

Open
#8,726 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug Feature: Sharing
Dominant language
JavaScript
Stars
1.2k
Forks
332
Avg merge
16h 13m
Merged PRs (30d)
137

Description

Steps to reproduce

Go to Administration settings -> Sharing.
Under "Limit sharing based on groups", select "Allow some groups" and restrict it to a specific group (e.g., "admin").
Under "Privacy settings for sharing", enable "Allow autocompletion to full match when entering the full name...".
Ensure that only "Also allow autocompletion on full match of the user email" is checked, while other full-match options (like User ID or Display name) are disabled.
Log in as a normal user who is NOT part of the allowed "admin" group.
Open the Calendar app, create a new event, and type single characters or letters into the "Attendees" search field.

Image
Expected behavior

The autocomplete should NOT show any users or email addresses, because sharing is restricted to admins, and incomplete matches are forbidden. This works perfectly in the Files app.

Actual behavior

The Calendar search field completely ignores these administrative restrictions. It queries the global user database and exposes full names and email addresses to unauthorized users immediately upon typing single characters.

Calendar app version

6.5.3

CalDAV-clients used

No response

Browser

Firefox 153.0.3

Client operating system

Windows 11

Server operating system

No response

Web server

None

Database engine version

None

PHP engine version

None

Nextcloud version

34.0.2

Updated from an older installed version or fresh install

None

List of activated apps

Nextcloud configuration

Web server error log

Log file

Browser log

Additional info

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Calendar Attendees autocomplete with the stated sharing and privacy restrictions, then compare its behavior with the Files app, which correctly enforces them. Trace the Calendar autocomplete entry point and its user search request. Done means unauthorized users receive no names or email addresses when incomplete matching is disabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.