b43da8d fix: check destination calendar write access on event update
📊 Changes
1 file changed (+6 additions, -0 deletions)
View changed files
📝backend/open_webui/routers/calendar.py (+6 -0)
📄 Description
update_event only verified write access on the event's source calendar. CalendarEventUpdateForm accepts a new calendar_id which the model layer applies unconditionally, so a user with write access to their own calendar could move (inject) an event into any other user's calendar. Mirror the destination check create_event already performs.
Contributor License Agreement
By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.
Note
Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/open-webui/open-webui/pull/24764
**Author:** [@Classic298](https://github.com/Classic298)
**Created:** 5/15/2026
**Status:** 🔄 Open
**Base:** `dev` ← **Head:** `fix/calendar-event-update-destination-authz`
---
### 📝 Commits (1)
- [`b43da8d`](https://github.com/open-webui/open-webui/commit/b43da8d6018874b7f64ac3a23b9116325d0483e9) fix: check destination calendar write access on event update
### 📊 Changes
**1 file changed** (+6 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `backend/open_webui/routers/calendar.py` (+6 -0)
</details>
### 📄 Description
update_event only verified write access on the event's source calendar. CalendarEventUpdateForm accepts a new calendar_id which the model layer applies unconditionally, so a user with write access to their own calendar could move (inject) an event into any other user's calendar. Mirror the destination check create_event already performs.
### Contributor License Agreement
<!--
🚨 DO NOT DELETE THE TEXT BELOW 🚨
Keep the "Contributor License Agreement" confirmation text intact.
Deleting it will trigger the CLA-Bot to INVALIDATE your PR.
Your PR will NOT be reviewed or merged until you check the box below confirming that you have read and agree to the terms of the CLA.
-->
- [x] By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](https://github.com/open-webui/open-webui/blob/main/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms.
> [!NOTE]
> Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/open-webui/open-webui/pull/24764
Author: @Classic298
Created: 5/15/2026
Status: 🔄 Open
Base:
dev← Head:fix/calendar-event-update-destination-authz📝 Commits (1)
b43da8dfix: check destination calendar write access on event update📊 Changes
1 file changed (+6 additions, -0 deletions)
View changed files
📝
backend/open_webui/routers/calendar.py(+6 -0)📄 Description
update_event only verified write access on the event's source calendar. CalendarEventUpdateForm accepts a new calendar_id which the model layer applies unconditionally, so a user with write access to their own calendar could move (inject) an event into any other user's calendar. Mirror the destination check create_event already performs.
Contributor License Agreement
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.