4.3

CVSS Score

3.1

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2026-54006

CVE-2026-54006: Open WebUI: Calendar event re-parenting allows writing events into another user's calendar

Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to 0.9.6, POST /api/v1/calendars/events/{event_id}/update validates that the caller has write access to the calendar the event currently belongs to, but does not validate the destination calendar_id supplied in the request body. The model layer then persists the new calendar_id unconditionally. A regular user-role account can therefore create an event in their own calendar and immediately move it into any other user's calendar whose ID they know — bypassing the authorization check that create_event correctly performs. This vulnerability is fixed in 0.9.6.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2026-54006

CVE-2026-54006:

4.3

CVSS Score

3.1

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

SSVC / BOD 26-04 ↗

Exploitation pocAutomatable NoTech Impact Partial

Select your environment

→SSVCDeferfix on upgrade

Runtime reachability resolves your actual outcome.Book a demo

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
open-webui	pip	<= 0.9.5	0.9.6

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability description clearly outlines an IDOR (Insecure Direct Object Reference) flaw in the event update functionality. The update_event function in backend/open_webui/routers/calendar.py is identified as the entry point. The core issue is that while it validates write access on the event's current calendar, it completely trusts the calendar_id provided in the request body for the destination, without checking if the user is authorized to write to that destination. This allows an attacker to reparent an event into another user's calendar. To pinpoint the exact fix, I compared the git tags for the last vulnerable version (v0.9.5) and the first patched version (v0.9.6). The commit ea058841c91dc38b6dd6d81463429a53282823cb with the message "fix: check destination calendar write access on event update" directly addresses this issue. The patch adds a crucial authorization check (_check_calendar_access) for the destination calendar_id within the update_event function, confirming it as the vulnerable function. The root cause is a failure to properly enforce authorization on all user-controlled inputs that specify a resource.

Vulnerable functions

open_webui.routers.calendar.update_event

backend/open_webui/routers/calendar.py

The function `update_event` was vulnerable to an Insecure Direct Object Reference (IDOR). It checked if the user had 'write' access to the calendar the event currently belonged to (the source calendar), but it failed to perform any authorization check on the destination `calendar_id` supplied in the request body. This allowed a user to move an event from a calendar they control to any other calendar in the system, as long as they knew the target calendar's ID. The patch added a check to ensure the user also has 'write' access to the destination calendar.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.