Browse / AI Framework and Platform Flaws / Cross-site scripting
Cross-site scripting
65 records in AI Framework and Platform Flaws.
- Kubeflow Pipelines: Reflected XSS in the frontend pod information and events error responses Pod name and namespace query values are echoed unescaped into HTML error responses, so a crafted link runs script in the frontend origin.
- LiteLLM vulnerable to reflected XSS in /sso/debug/callback
- unstructured: Stored XSS via unescaped HTML generation
- Open WebUI: Same-origin XSS to account takeover via terminal port-preview iframe hardcoding allow-same-origin
- Open WebUI: Same-origin XSS to account takeover via terminal file-preview iframe hardcoding allow-same-origin Terminal-served HTML previews run in an iframe that grants same-origin access, so scripts in the file run in the app origin and can read the session token.
- Open WebUI: Stored XSS via unescaped KaTeX render-error fallback in rendered messages
- n8n: Stored DOM XSS via Resource Locator `cachedResultUrl` A workflow's cachedResultUrl is passed to window.open without scheme checks, so a javascript URL runs script when a victim opens it.
- n8n: DOM-Based XSS via Unsandboxed iframe srcdoc in HTML Preview
- Open WebUI allows limited stored XSS vila uploaded html file A low-privileged user uploads an HTML file containing script that runs in another user's browser when the file is opened.
- Open WebUI vulnerable to Stored XSS via iFrame embeds in response messages
- Open WebUI vulnerable to Stored XSS via iFrame in citations model
- Open WebUI: Stored XSS to Account Takeover via Model Profile Images
- n8n: Stored XSS in Chat Trigger Node A user with workflow edit rights sets a malicious webhook ID that injects script into the chat page, which then runs for anyone who opens it.
- n8n: Reflected XSS via Facebook, WhatsApp, and Microsoft Teams Trigger Webhook Verification Endpoints
- n8n: Same-Origin XSS in Respond to Webhook Node
- Open WebUI has XSS via SVG in /api/v1/channels/webhooks/{webhook_id}/profile/image A webhook profile image URL accepts an SVG data URI that is served unsanitised as image/svg+xml, so embedded script handlers run in the app origin.
- Open WebUI vulnerable to stored XSS via OAuth picture claim stored as SVG data URI in profile_image_url The OAuth login path stores a remote picture as an SVG data URI that skips the image validator and is served inline, so its script runs on the app origin.
- Open WebUI has Stored Cross-Site Scripting In Profile Picture Profile image data URIs with arbitrary MIME types are served from the app origin, so an embedded SVG script runs for anyone who views the image.
- Open WebUI has stored XSS via unsanitized Office/Excel/DOCX file preview rendering ({@html} without DOMPurify)
- Open WebUI has Stored XSS in Banner Component via Improper Sanitization Order Banner content is sanitised before Markdown conversion, so a link produced afterwards carries a javascript: URL that is rendered unescaped.
- Open WebUI Has Stored Cross-Site Scripting in SVG Renderer
- Open WebUI has Stored XSS in Pending User Overlay via Incorrect DOMPurify Application Order Running the sanitiser before Markdown parsing lets javascript: links created during parsing reach the page unfiltered, enabling stored script execution.
- parisneo/lollms vulnerable to stored XSS in the social feature Social feed post content is stored without sanitisation and rendered to viewers, so injected script runs in their browsers.
- n8n has XSS in its Credential Management Flow A crafted OAuth2 credential with a javascript: URL in the authorization URL field runs script in the browser of a victim who clicks the authorize button.
- n8n has XSS in Chat Trigger Node through Custom CSS Custom CSS in the Chat Trigger node is stored after a misconfigured sanitize-html pass, allowing script to run on the public chat page.
- n8n has a Stored XSS Vulnerability in its Form Trigger
- n8n: Authenticated XSS and Open Redirect via Form Node
- n8n Vulnerable to XSS via Binary Data Inline HTML Rendering
- n8n Vulnerable to Stored XSS via Various Nodes A workflow author embeds script in node-rendered pages such as forms and chat, which then runs for any visitor.
- n8n's Improper CSP Enforcement in Webhook Responses May Allow Stored XSS The CSP sandbox is not applied to some webhook and HTTP responses, so an author's HTML runs with the origin's privileges for other users.
- n8n Has Stored Cross-site Scripting via Markdown Rendering in Workflow UI
- Label Studio is vulnerable to full account takeover by chaining Stored XSS + IDOR in User Profile via custom_hotkeys field Stored script injected through a hotkey setting runs in other users' browsers, and missing CSRF protection lets it steal API tokens.
- n8n's Possible Stored XSS in "Respond to Webhook" Node May Execute Outside iframe Sandbox
- Open WebUI Vulnerable to Stored DOM XSS via Note 'Download PDF' SVG markup in imported Markdown is inserted into the PDF export via innerHTML without sanitising, so script runs in the exporting user's session.
- Flowise is vulnerable to stored XSS via "View Messages" allows credential theft in FlowiseAI admin panel Chat message content is rendered unsanitised in the admin message viewer, so injected script runs for the admin and can read localStorage.
- Stored XSS in n8n LangChain Chat Trigger Node via initialMessages Parameter
- Stored XSS in n8n Form Trigger allows Account Takeover via injected iframe and video/source
- label-studio vulnerable to Cross-Site Scripting (Reflected) via the label_config parameter. A crafted label_config posted to the upload-example endpoint is reflected into a response the browser renders, running script in the victim's session.
- n8n Vulnerable to Stored XSS through Attachments View Endpoint The attachment view endpoint lets callers choose the response MIME type, so an uploaded HTML file can be served as text/html and run script.
- one-api Cross-site Scripting vulnerability
- LocalAI Cross-Site Scripting (XSS) vulnerability in its search functionality
- AgentScope stored cross-site scripting (XSS) vulnerability A user-controlled run identifier is rendered into the run inspection page as raw HTML, so attacker script runs in viewers' browsers.
- Open WebUI stored cross-site scripting (XSS) vulnerability
- Open WebUI Vulnerable to Cross-Site Scripting (XSS) via Chat File Upload
- Label Studio allows Cross-Site Scripting (XSS) via GET request to `/projects/upload-example` endpoint
- LocalAI Cross-site Scripting vulnerability
- Lollms vulnerable to Cross-site Scripting The SVG sanitiser removes only script tags and on-event attributes, so other SVG vectors survive and run script when a victim opens the file.
- Gradio has an XSS on every Gradio server via upload of HTML files, JS files, or SVG files
- Flowise and Flowise Chat Embed vulnerable to Stored Cross-site Scripting
- MindsDB Cross-site Scripting vulnerability Script stored in engine, database, project or dataset names runs in the browser of any user who lists them in the web UI.