Browse / AI Framework and Platform Flaws / Cross-site request forgery
Cross-site request forgery
8 records in AI Framework and Platform Flaws.
- New API is vulnerable to CSRF through user email binding Account binding actions use GET requests, so a cross-site navigation can make a logged-in user's browser bind attacker-controlled email or OAuth identities.
- Open WebUI: Cross-origin postMessage confirmation bypass via action:submit The chat page message listener accepts prompt and submit messages from any origin, so an external page can submit prompts and trigger model requests without the confirmation dialog.
- Flowise: Hardcoded CORS wildcard on TTS endpoint enables cross-origin credential abuse from any webpage A hardcoded wildcard CORS header on the TTS endpoint lets any website make cross-origin requests that use stored credentials.
- Open WebUI Vulnerable to Cross-Site Request Forgery (CSRF) via Image URL Manipulation Attacker-chosen image URLs in profile and model pictures are fetched automatically when viewed, sending authenticated GET requests to attacker endpoints.
- Cline Kanban Server has a Cross-Origin WebSocket Hijacking Vulnerability Local WebSocket endpoints skip Origin validation, so any visited website can read agent data and inject input into running agent terminals.
- MLflow Cross-Site Request Forgery (CSRF) vulnerability The signup endpoint accepts cross-site form submissions without anti-CSRF checks, so a third-party page can make a victim's browser create accounts.
- Open WebUI Vulnerable to Cross-Site Request Forgery (CSRF) Destructive reset and delete actions run on GET requests, so a malicious page or top-level link can trigger them in a logged-in user's browser.
- Gradio applications running locally vulnerable to 3rd party websites accessing routes and uploading files A locally running Gradio server accepts requests from arbitrary websites, so a visited page can upload files to the user's machine.